using-agent-skills

To route a development task, you map the incoming request to the appropriate phase-specific skill, such as idea refinement, specification, planning, implementation, testing, or shipping. This ensures work begins with the correct process and prevents common engineering mistakes.

The best way to manage assumptions during the software engineering process is to enforce explicit assumption surfacing and active confusion management before advancing. This operational guardrail surfaces hidden errors early, reducing rework and ensuring scope discipline.

To chain multiple engineering skills for an end-to-end feature, you sequence lifecycle skills into a standard workflow progression from idea refinement through shipping. Lifecycle coordination allows chaining multiple skills or selecting a minimal subset for focused tasks like bug fixes.

Yes, you need to verify task completion before moving to the next development phase. Mandatory verification steps are enforced before advancing to ensure scope discipline, simplicity, and that hidden errors are caught early across the engineering workflow.

Yes, you can use skill discovery for focused tasks like code reviews instead of full lifecycle coordination. The system allows selecting a minimal subset of phase-specific skills for focused tasks, preventing the overhead of chaining the entire end-to-end workflow.