speckit-implement

To execute implementation tasks from a markdown file, run the skill in your repo root to load tasks.md, validate prerequisite checklists, and coordinate phased execution. It reads the plan definitions and enforces dependency- and parallel-aware sequencing rules automatically.

Yes, you can run custom hooks during project bootstrapping by defining them in your .specify/extensions.yml file. The execution flow optionally triggers configured pre-implement and after_implement extension hooks before and after running the core task phases.

The best way to coordinate parallel task execution is to use a plan-driven skill that reads parallel task markers directly from tasks.md. It applies file-based sequencing rules to manage dependencies and reports progress as each phase completes.

You validate checklist completion status by running pre-implementation guardrails that check prerequisites via the repository script. This ensures all required checklist items are verified before executing the planned task phases from tasks.md.

Yes, this implementation planning approach works for repository modernization, feature buildouts, integration work, and polish completion scenarios. It executes the project plan by coordinating task phases and marking tasks complete as they finish.

Implementation workflows stall during task orchestration when lacking a reliable way to execute planned tasks and validate prerequisites. Using a plan-driven execution skill resolves this by enforcing dependency-aware sequencing, validating checklists, and applying project hooks.