name: flutter-feature-bootstrap description: Scaffold a new Flutter feature module (folders + starter files + tests) to remove repetitive manual project setup work. triggers: - "bootstrap flutter feature" - "scaffold new flutter module" - "create feature folders and test stubs" inputs: - "feature name via --feature=<name>" - "mode flag: --dry-run | --execute | --verify-only" outputs: - "new feature folders/files under lib/features and test/features" safety: - "execute requires clean git tree" - "dry-run first to preview generated structure" commands: - "skills/flutter-feature-bootstrap/scripts/run.sh --dry-run --feature=checkout" - "skills/flutter-feature-bootstrap/scripts/run.sh --execute --feature=checkout"

When to use / when NOT to use

•Use when starting a new feature and you want consistent scaffolding.
•Do not use when repository has a custom architecture template that differs.

Preconditions (tools, versions, repo state)

•Flutter repo with pubspec.yaml.
•Feature name provided via --feature.
•Clean tree for --execute.

Workflow (DISCOVER → PLAN → EXECUTE → VERIFY → REPORT)

•DISCOVER: confirm project and feature target.
•PLAN: preview directories/files to generate.
•EXECUTE: create feature structure and test stubs.
•VERIFY: list generated artifacts.
•REPORT: summarize what was scaffolded.

Exact commands and expected signals

bash

skills/flutter-feature-bootstrap/scripts/run.sh --dry-run --feature=payments
skills/flutter-feature-bootstrap/scripts/run.sh --execute --feature=payments
skills/flutter-feature-bootstrap/scripts/run.sh --verify-only --feature=payments

Success: feature folder and starter files created in execute mode. Failure: missing --feature, dirty tree, or invalid project context.

If it fails (checklist)

•Provide a valid kebab/snake feature name.
•Ensure git working tree is clean.
•Check write permissions.

Final report template

•Feature requested.
•Files/folders created.
•Follow-up manual wiring steps.
•Rollback command.