using-rolepod

To route software development requests correctly, this Skill classifies incoming tasks and directs them to the appropriate phase in the Define, Plan, Build, Verify, Review, or Ship lifecycle. It prevents tasks from jumping straight into coding without proper planning.

To prevent skipping code review and verification, this Skill enforces phase selection and skip rules. It requires explicit exit evidence for skipped gates, ensuring lightweight handling for trivial edits while maintaining strict workflow discipline for complex changes.

Workflow routing handles high-risk tasks like security and migration updates by applying strict guardrails. It automatically escalates sensitive work involving authentication or billing into stronger review and enforces stricter workflow discipline to prevent critical errors.

Yes, you can force a full-lifecycle software delivery run using the full-lifecycle mode. This mode supports a forced end-to-end path, ensuring every phase from specification and planning to verification, review, and shipping runs in sequential order without normal shortcuts.

For a repo-wide codebase audit, the correct workflow routing approach uses a scope-then-spawn pattern. This method handles large sweeps and investigations sequentially to avoid wasteful parallelization across the repository.

Yes, you need workflow routing for vague feature requests and refactoring tasks to determine the correct starting phase. It evaluates the request and routes it to specification, planning, or implementation before any editing begins, ensuring structured handoff to downstream skills.