using-agent-skills

To find the right engineering workflow, describe your current task phase and intent to the agent, such as planning, spec definition, implementation, or debugging. The skill then recommends a matching guided path like spec-driven-development or incremental-implementation to enforce scope discipline and verification.

The best way to manage scope and assumptions during software implementation is using a guided workflow that enforces assumption surfacing and active confusion management. Process guardrails ensure simplicity and require explicit verification steps before task completion.

Yes, you can chain multiple engineering process skills together. Workflow chaining supports multi-skill sequences, allowing a larger task to move from definition to planning, implementation, review, and shipping without skipping verification steps.

Yes, selecting a spec development workflow requires a YAML-defined skill identity containing a name and description. This definition operationally enforces scope discipline, simplicity, and explicit verification steps before the engineering process concludes.

Your engineering process skips verification because it lacks enforced process guardrails. Applying a structured workflow skill enforces explicit verification steps, ensuring assumptions are surfaced and confusion is actively managed before shipping.

You need to switch from a planning workflow to a debugging flow when your current task intent changes from defining specs to resolving active issues. The skill discovery mechanism matches your new context to the appropriate engineering process, enforcing scope discipline.