hyper-plan

To break down a coding task into an implementation plan, this skill dispatches a planner agent to generate an ordered, bite-sized decomposition saved under .hyperclaude/plans/. It transforms non-trivial feature requests into structured, runnable steps without getting stuck on scope.

For oversized software engineering tasks, this skill generates an epic roadmap saved under .hyperclaude/epics/ instead of a standard plan. It structures massive workloads into manageable milestones while preserving dependency context for later expansion.

Task planning maintains research traceability by deterministically matching research artifacts via frontmatter slug. This ensures your code implementation plan, review, and research documents stay linked throughout the agent orchestration workflow.

Yes, you can expand an existing epic roadmap milestone while carrying the roadmap's Depends on context into later detailed plans. This epic-aware milestone expansion ensures subsequent implementation tasks remain connected to the original scope.

You should avoid automated task decomposition for one-step tasks or when a recent plan already covers the work. The skill applies practical skip rules to avoid unnecessary replanning for simple coding implementations.

The best way to plan an OAuth login feature is to run the skill with your task description to generate a structured, ordered decomposition plan. This produces a multi-task implementation roadmap that handles the non-trivial scope of API authentication.