plan-implementation

SDK feature implementation planning is an end-to-end pipeline that enforces mandatory phases 0 through 6 to validate feature designs. You need it when coordinating complex extraction from existing codebases or building greenfield features to ensure no critical planning step is skipped.

To plan and validate SDK feature implementations, run the workflow to read living docs like CLAUDE.md and PLAYBOOK.md, then execute phases 0-6 to produce comprehensive plan and requirements documents in the Docs directory ready for downstream implementation.

Yes, you can extract implementation requirements from an existing codebase using Mode A workflow, which handles data extraction and validation. It analyzes your current codebase to generate structured requirements and plan documents for the feature pipeline.

Yes, the SDK planning workflow consults living docs like CLAUDE.md, PLAYBOOK.md, and REACT_ROADMAP.md to enforce mandatory planning phases. These references provide the architectural context required to generate validated implementation plans and requirements.

The best way to document greenfield feature ideas is using Mode B workflow, which processes new feature concepts through phases 0-6. It generates standardized plan-implementation-plan.md and requirements documents to prepare your ideas for the implement-feature workflow.

The SDK implementation planning pipeline generates Docs/plans/plan-implementation-plan.md and Docs/plan-implementation-requirements.md. These validated output documents coordinate multi-agent research and are structured to feed directly into the downstream implement-feature workflow.