plan-implementation

To turn a feature specification into an implementation plan, you run the planning skill on your spec. It orchestrates planning specialists to generate a primary plan file and companion artifacts for structured engineering work.

Maintaining traceability across feature implementation iterations is achieved by recording decisions and progress in structured artifacts. The process generates an implementation-iteration-history file and a decision log to document the structured drafting steps.

Documenting implementation decisions and open questions during project planning is handled by generating a decision-log artifact. This evidence-based workflow captures artifact-backed decisions and surfaces open questions for later resolution.

Yes, you can coordinate project-manager-led planning sessions directly from a feature spec. The planning orchestration converts your specification into a deliverable plan and companion artifacts to guide development.

Artifacts generated when planning a feature implementation from a spec include the primary feature-implementation-plan file, an implementation-decision-log, and an implementation-iteration-history file to ensure full project traceability.

Feature implementation planning requires no external dependencies or environment setup. You simply provide a feature specification, and the skill orchestrates the planning specialists to produce the actionable plan and tracking artifacts.