Results for “markdown-plan”
8 skillsPrd To Plan
Breaks a PRD into a multi-phase implementation plan using tracer-bullet vertical slices, saved as a local Markdown file in ./plans/.
20
Create Implementation Plan
Generate structured, machine-readable implementation plans for features, refactoring, upgrades, or infrastructure changes.
36.2k
Update Implementation Plan
Update an existing implementation plan file with new or updated requirements for features, refactoring, package upgrades, design, architecture, or infrastructure.
36.2k
More results
Breakdown Feature Implementation
Creates detailed technical implementation plans for features based on a Feature PRD, including system architecture, database schema, API design, and frontend component hierarchy.
36.2k
Plan C
Continues deep iteration on an existing planning document: detects explicit file-loading intent, provides status summaries, and supports on-demand in-depth exploration.
32
Breakdown Feature Prd
Takes a high-level feature from an Epic and generates a detailed Product Requirements Document (PRD) in Markdown, covering goals, user stories, requirements, and acceptance criteria.
36.2k
Blueprint
Generate a step-by-step construction plan from a one-line objective, with dependency graphs, parallel step detection, and adversarial review for multi-session engineering projects.
226k
Breakdown Epic Pm
Translates high-level ideas into detailed Epic-level Product Requirements Documents (PRDs) that serve as the single source of truth for engineering teams.
36.2k