skills.rest
jeremysball
jeremysballCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

prd-exec

Creates test-first execution plans with atomic, verifiable tasks for PRD implementation milestones.

Updated Nov 7, 2024
Search Tags:#tdd#project planning#task breakdown#test-driven development#prd#milestone tracking#execution plan
One-click install
npx skills add https://github.com/jeremysball/dotfiles --skill prd-exec-jeremysball
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prd-exec
Source: https://github.com/jeremysball/dotfiles/tree/main/.pi/skills-archive/prd-exec
Command: npx skills add https://github.com/jeremysball/dotfiles --skill prd-exec-jeremysball

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Large PRD milestones are hard to execute reliably without a structured breakdown. This Skill converts a PRD milestone into a granular, test-first execution plan where every task is atomic, independently verifiable, and maps to a single commit. ## Core Features & Use Cases - Test-First Task Breakdown: Splits milestones by boundary into test, implement, and verify steps following red-green TDD discipline. - PRD Auto-Detection: Detects the target PRD from an argument, git branch name, recent commits, or modified files. - Plan Quality Self-Review: Enforces a checklist covering success signals, repo constraints, validation workflow, and behavior-first tests. - Use Case: You are starting Phase 2 of PRD #76 (a SQLite storage layer). Run the skill to generate prds/execution-plan-76-phase2.md with atomic test-first tasks, then work through them one commit at a time. ## Quick Start Ask the agent to create an execution plan for PRD 76 by running /prd-exec 76 and it will analyze the PRD and generate a test-first task plan.

Frequently Asked Questions about prd-exec

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

FAQPage Schema
How do I create a test-first execution plan for a PRD?▼

Run /prd-exec with the PRD number, such as /prd-exec 76. The skill reads the PRD, identifies the current incomplete milestone, and writes a plan to prds/execution-plan-[id]-[phase].md with test, implement, and verify steps per task.

How does the skill detect which PRD to plan for?▼

It checks the prdNumber argument first, then the git branch name for feature/prd-<id>-* patterns, then recent commit messages, then modified files matching prds/<id>-*.md. If none match, it asks the user directly.

What makes a good task in an execution plan?▼

Each task should be atomic and independently verifiable: one test describing observable behavior, one minimal implementation, and one targeted verification command. Tasks should prove the milestone outcome, not just check that files or exports exist.

What happens if I forgot to write the test first?▼

The skill defines a recovery path: write a test for the existing behavior, verify it passes, commit it as 'test: verify existing behavior of X', then continue with test-first discipline for remaining tasks.

When should I not use an execution plan?▼

Skip it for time-boxed spike explorations, pure refactors where tests already exist, and genuinely trivial wiring changes. The skill is designed for milestones with more than three implementation steps or multiple files.

Related Skills

Explore More Software Engineering Skills→
finleysgfinleysg

write-a-prd

Generate a structured PRD JSON file from a problem description.

Community
Intermediate
MadAppGangMadAppGang
7

implement

Execute development tasks with TDD, Git commits, and progress tracking.

Official
Advanced
RonanCodesRonanCodes

ralph

Execute PRD-driven task loops with progress tracking and validation.

Community
Advanced
tDaliletDalile

gsd:add-todo

Add todo items with titles and metadata to a tracking list.

Community
Basic