dev-plan

Generates phased implementation plans from feature requests or bug reports.

Updated Mar 9, 2026
One-click install
npx skills add https://github.com/GinoCanessa/dotnet-fhir-packages --skill dev-plan-ginocanessa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-plan
Source: https://github.com/GinoCanessa/dotnet-fhir-packages/tree/main/.github/skills/dev-plan
Command: npx skills add https://github.com/GinoCanessa/dotnet-fhir-packages --skill dev-plan-ginocanessa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a raw feature request or bug report into an executable engineering plan requires senior-level judgment about phases, file ownership, verification commands, and risk. This Skill acts as a staff-level Engineering Lead that reads a featurerequest.md or bugreport.md and produces a structured, reviewable plan.md that an engineer or an execution skill can follow end-to-end. ## Core Features & Use Cases - Phased plan generation: Produces a plan.md with problem recap, approach, alternatives, per-phase owned paths, verification commands taken verbatim from AGENTS.md, tests, risks, and rollback steps. - Slot-based workflow: Accepts a full path or a short slot number that expands to scratch/<MMDD>-<##>/, auto-discovering the source request and any sibling approach.md decision artifact. - Iteration and critique: Refines existing plans without rewriting completed phases, runs an adversarial critique on non-trivial plans, and offers an interactive walkthrough of open questions. - Use Case: After drafting a bug report with dev-report, invoke this Skill with the slot number to get a phased, independently verifiable implementation plan ready for dev-do to execute. ## Quick Start Ask the assistant to run the dev-plan skill on slot 2 to turn the bug report in that scratch slot into a phased implementation plan.

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?

Invoke the skill with the path to your bugreport.md or a slot number that expands to scratch/<MMDD>-<##>/. It reads the report, checks for a sibling approach.md, and writes a phased plan.md with owned paths and verification commands in the same directory.

How do I plan a feature from a feature request document?

Provide the path to featurerequest.md or its slot number. The skill acts as an Engineering Lead, commits to an approach with justified alternatives, and drafts plan.md with phases, tests, risks, and rollback steps grounded in your repository's AGENTS.md conventions.

Can I refine an existing plan instead of starting over?

Yes. If plan.md already exists at the resolved location, the skill enters iteration mode: it preserves phases marked In-progress or Complete, edits pending phases in place, and folds in new feedback or review findings as additional phases.

Does the skill modify my feature request or bug report files?

No. Source files like featurerequest.md, bugreport.md, and approach.md are strictly read-only. If they need changes, the skill tells you to re-invoke the authoring skill rather than editing them itself.

What happens when a plan has unresolved open questions?

The skill offers an interactive walkthrough, presenting each open question one at a time with at most three concrete answers, a single recommendation, and a free-form option. Answered decisions are written into the plan before moving to the next question.