Adding Module Awareness To Our Planprd Skill.mp4

Commits:

# Start the lesson — module awareness added to write-a-prd skill
pnpm reset 08.10.01
pnpm cherry-pick 08.10.01

Adding Module Awareness To Our Planprd Skill

Preventing bad architecture is better than fixing it later. Right now, when you're building features with an agent, you might be creating shallow modules that are hard to test and change.

The issue is that module decisions usually happen during implementation, not before it. By then, it's too late to fix the architecture.

The solution is to add a planning phase where you intentionally sketch out the modules you'll need before you start writing code. This is called module awareness, and it prevents shallow modules from invading your codebase at source.

Steps To Complete

Review the Updated /to-prd Skill

• [ ] Check out the changes to the /to-prd skill at .claude/skills/to-prd

The /to-prd skill has been updated from a 2-step process to a 3-step process. There's now a module awareness phase.

• [ ] Read through the new module planning step

Just before writing the template, the skill now instructs the agent to:

• Sketch out the major modules you will need to build or modify
• Actively look for opportunities to extract deep modules that can be tested in isolation
• A deep module encapsulates a lot of functionality in a simple testable interface that rarely changes
• Check with the user that these modules match their expectations

This brings module awareness into the most important moment: when you're designing the new implementation.

(Optional) Test the Updated Skill