dev-plan

Generates phased implementation plans from bug reports or feature requests.

154|57|Updated Feb 7, 2020
One-click install
npx skills add https://github.com/FHIR/fhir-codegen --skill dev-plan-fhir
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dev-plan
Source: https://github.com/FHIR/fhir-codegen/tree/main/.github/skills/dev-plan
Command: npx skills add https://github.com/FHIR/fhir-codegen --skill dev-plan-fhir

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a raw bug report or feature request into an executable, reviewable implementation plan requires senior engineering judgment and is often skipped or done inconsistently. This Skill acts as a staff-level Engineering Lead, producing a structured plan.md with phases, owned paths, verification commands, risks, and rollback steps that an engineer or an execution skill can follow end-to-end. ## Core Features & Use Cases - Phased Plan Generation: Reads a featurerequest.md or bugreport.md (by full path or scratch slot number) and writes a plan.md with per-phase goals, owned paths, steps, and verification commands taken verbatim from AGENTS.md. - Approach-Aware Planning: When a sibling approach.md from dev-approach exists, plans from its selected shape or override block instead of re-deriving alternatives. - Iteration & Open Questions Walkthrough: Refines existing plans without disturbing completed phases, and interactively walks the user through open questions one at a time with recommended answers. - Use Case: After filing a bug report in scratch/0115-02/, invoke the skill with slot 2 to get a Ready-to-execute plan with concrete file-level steps and test commands, then hand it to dev-do for implementation. ## Quick Start Ask the AI to build an implementation plan from the bug report in scratch slot 2 using the dev-plan skill.

Frequently Asked Questions about dev-plan

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

FAQPage Schema
How do I turn a bug report into an implementation plan?▼

Provide the path to a bugreport.md or featurerequest.md, or just a slot number that expands to scratch/<MMDD>-<##>/. The skill reads the source, inspects the relevant code, and writes a phased plan.md with verification commands in the same directory.

How to plan a feature before writing code with an AI assistant?▼

Author a featurerequest.md first, then invoke this skill with its path or slot number. It acts as an Engineering Lead, committing to an approach, naming specific files and tests, and producing a plan an engineer or the dev-do skill can execute.

Does dev-plan work without a dev-approach artifact?▼

Yes. When no approach.md exists in the slot, the skill offers dev-approach once and then plans directly from the source request. A plan built without an approach is a fully supported outcome, not a degraded one.

Can I update an existing plan without losing completed phases?▼

Yes. Iteration mode preserves any phase marked In-progress or Complete, edits still-Pending phases in place, and folds in review findings from analysis.md as new remediation phases rather than rewriting executed work.

What are the limitations of the dev-plan skill?▼

It does not implement code, run full builds, or commit anything; execution belongs to dev-do. It also treats source requests and approach artifacts as read-only and never invents build or test commands not documented in AGENTS.md.