m-sdd-plan

You can automate technical implementation plan generation by creating a Markdown file from an approved specification and enforcing human approval gates before proceeding to development tasks.

The best way to add human approval gates to software development is to require explicit user approval for architecture decisions and task decomposition after automatically generating the technical plan.

Yes, you need jq installed as a dependency to run the feature plan generation scripts and process the specification data required for the technical planning workflow.

Yes, you can generate companion artifacts like research notes, data models, and contracts automatically alongside the implementation plan when the feature specification is approved.

To generate a technical plan for a specific feature, run the plan command with the feature identifier to produce the Markdown plan and require human approval before moving to the next phase.