Updating Our PRD And Plan Skill To Use GitHub.mp4

Commits:

# Start the lesson - PRD and plan skills updated to use GitHub
pnpm reset 07.09.01
pnpm cherry-pick 07.09.01

Updating Our PRD And Plan Skill To Use GitHub

You've seen how bug reports can live in GitHub issues. But what about new features? How do PRDs and plans fit into this workflow?

The answer is to move everything into GitHub. Instead of creating PRDs and plans as local files, create them as GitHub issues. This lets your AFK agent see the entire backlog and make smarter decisions about what to work on next.

The Power of Parallelizing Planning and Implementation

By keeping your PRDs and plans in GitHub, you enable something powerful: you can parallelize planning with implementation.

Your AFK agent can look at the entire backlog - new features, bug fixes, infrastructure work - and use its task selection prompt to figure out what to do next. Whether that's critical bug fixes, development infrastructure, or tracer bullets for new features.

And because everything lives in GitHub, you can do your entire planning loop without touching the codebase or creating local files that might interfere with an agent working in the code.

What Changed

The skills in .claude/skills/write-a-prd/SKILL.md and .claude/skills/prd-to-plan/SKILL.md have been updated.

Instead of creating local files, they now create GitHub issues. The template is exactly the same - the only difference is where it's published.

This means your AFK agent will look at the entire backlog - new features, bug fixes, infrastructure - and use its task selection prompt to figure out what to do next.

Planning loop showing GitHub issues workflow

You can now do your entire planning loop without touching the codebase. Create PRDs and plans in GitHub, and your AFK agent picks them up from the backlog.

Steps To Complete