p:feature-plan

Name: p:feature-plan
Availability: InStock
Author: pontscho

Generate a feature implementation plan with five checkpoints and dual validation loops.

1|Updated Jan 7, 2026

Search Tags:#planning #architecture #documentation #validation #handoff #codebase-exploration

Ready to run

npx skills add https://github.com/pontscho/prompt-heaven --skill p-feature-plan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: p:feature-plan
Source: https://github.com/pontscho/prompt-heaven/tree/main/ClaudeCode/skills/p%3Afeature-plan
Command: npx skills add https://github.com/pontscho/prompt-heaven --skill p-feature-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architect-driven feature planning streamlines the path from codebase understanding to a formal implementation plan, ensuring alignment with architecture and security review processes.

Core Features & Use Cases

Interactive, architecture-aware planning that explores the repository via p:minion-explorer and captures design patterns, decisions, and risks.
Five-checkpoint clarification workflow that surfaces questions and converges on a comprehensive feature-implementation-plan.md.
Dual validation loops: Phase A (plan-inspector for correctness) and Phase B (security review) before presenting a refinement menu.
Handoff-friendly output to enable downstream engineers to implement the plan without ambiguity.

Quick Start

Follow the interactive prompts to generate a complete feature-implementation-plan.md for the target codebase.

Frequently Asked Questions about p:feature-plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I create a feature implementation plan that aligns with existing codebase architecture?▼

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.

What is the best way to validate a software feature plan for security and correctness before handoff?▼

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.

How does architecture-aware feature planning work when exploring an unfamiliar repository?▼

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.

Can I generate handoff-ready documentation for downstream engineers from a feature planning session?▼

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.

What limitations should I expect when using an automated architect-driven feature planning process?▼

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.

Do I need a specific codebase exploration tool to start the feature planning workflow?▼

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.