dev-docs

Run /dev-docs with the path to your plan file in docs/plans/. It creates a feature branch, generates plan, context, and task files under docs/active/<name>/, commits the initialization, and hands off to the dev-autopilot workflow.

The Skill stops and instructs you to run /dev-plan first. It refuses to invent phases or tasks because the execute workflow's planner needs Implementation Units from docs/plans/ to delegate work to builders.

The autopilot, execute, and review workflows grep for lines matching ^- [ ] to track progress. An indented checkbox is invisible to these parsers, which would silently break phase completion detection and E2E prechecks.

Each [E2E] scenario becomes one flat checkbox line containing the Maestro flow path and optional seed file. These are excluded from execute completion counting and are only checked off after a real Maestro run passes during review.

Yes, it detects the existing folder as a resumption, shows the current autopilot state and completed phases, and asks whether to regenerate only missing files. It never overwrites a task file that contains progress.

It verifies three things: whether E2E scenarios exist and .env.e2e is configured, whether blocking operator preparation items are unchecked, and whether the git tree is clean on the feature branch. Red items must be resolved and committed first.