speckit-implement

To implement features from a GitHub issue spec automatically, you provide the issue number to execute a structured task checklist, enforcing issue tracking and pre-execution checks to guide development.

Yes, you can enforce mandatory GitHub issue numbers before starting an implementation workflow. The system requires a valid issue input to execute the issue-backed task checklist and apply constitution-rule validation.

An issue-backed spec is a development plan linked directly to a GitHub issue. It guides software development by driving end-to-end code implementation through a structured checklist, ensuring traceability from issue to code.

Yes, implementing code from a spec supports automated checks and living docs loading. The workflow applies pre-execution hook checks and loads living documentation to inform development context during execution.

Automating code implementation from an issue-backed spec requires a pre-existing GitHub issue and an attached plan to function. Without mandatory issue input and living docs, the execution workflow cannot properly validate or guide the coding process.