What problem does it solve? Feature planning often happens in scattered chat threads and gets lost, making it hard to track decisions, assumptions, and progress. This Skill maintains a single versioned plan document that records requirements, design decisions, open questions, and implementation status in one consistent format. ## Core Features & Use Cases - Plan Document Generation: Creates a structured plan file with status dashboard, requirements, phased implementation steps, QA plan, and change history when given a file path that does not yet exist. - Q&A-Driven Updates: Reads user comments and questions left inside the plan file and converts them into a discussion log with documented decisions, alternatives considered, and rationale. - Built-in Review Gates: Enforces reuse-first checks, over-engineering guards, security gates (trust boundaries, idempotency, secrets, rollback), and a self-critique section that lists open questions and assumptions before implementation begins. - Use Case: A developer starts a new feature, runs the skill to draft a plan, annotates the file with questions over several days, and watches the document evolve through versioned updates until it is ready for implementation. ## Quick Start Run /checkmd with a plan file path to create a new implementation plan or update an existing one based on my inline comments.
