p:feature-plan

To create an architecture-aligned feature implementation plan, this skill guides codebase exploration, captures design patterns, and enforces five clarification checkpoints to produce a comprehensive feature-implementation-plan.md document.

Validating a software feature plan for security and correctness requires dual validation loops: a Phase A plan-inspector for correctness and a Phase B security review, ensuring the final handoff contract is free of ambiguity.

Architecture-aware feature planning works by interactively exploring the repository, capturing existing design patterns and risks, and converging through a five-checkpoint clarification workflow to align new features with current structures.

Yes, you can generate handoff-ready documentation because the planning process outputs a formal feature-implementation-plan.md file that captures all decisions, patterns, and risks for downstream engineers to implement without ambiguity.

Limitations of automated architect-driven feature planning include dependency on interactive prompts for capturing context and the necessity of completing both Phase A and Phase B validation loops before the final refinement menu appears.

The feature planning workflow integrates directly with the p:minion-explorer tool to conduct repository exploration, ensuring that design patterns and architectural decisions are accurately captured before generating the implementation plan.