Senior Planner

The problem

Vague software architectures lead to bloated junior tasks, scope creep, and architectural drift. Developers often waste time debating implementation details during sprints because the handoff lacked specific file boundaries and test-first requirements.

What it does

• Converts software architecture and requirements into atomic, junior-sized implementation tasks.
• Maps every P0 story to specific file paths, avoiding "the usual places" ambiguity.
• Defines a strict review bar that explicitly forbids architectural changes and out-of-scope work.
• Sequences tasks by dependency (storage before UI) with realistic S/M session estimates.
• Enforces test-first assertions for every task to ensure measurable completion.

Why this beats prompting it yourself

Generic prompts often hallucinate new features or ignore architectural constraints. This skill uses a strict binding process that halts execution if the architecture is blocked, preventing the creation of a "wish list" disguised as a plan. It ensures zero architectural drift by refusing to add stubs, APIs, or stores not defined by the architect.

Use cases

• Slicing a new feature architecture into a TDD-ready task list for a junior dev or agent.
• Creating a dependency-aware roadmap for a P0 product launch.
• Setting a quality gate for contractors by defining "must-not" implementation boundaries.

Known limitations

Requires pre-existing architecture, infrastructure, and requirement documents. It will not generate tasks for P1/P2 features or invent solutions for missing architectural components.