using-agent-skills

Discovers and routes tasks to phase-specific engineering workflow skills.

Updated Jul 1, 2026
One-click install
npx skills add https://github.com/raishoemi/traffic-sim-v2 --skill using-agent-skills-raishoemi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: using-agent-skills
Source: https://github.com/raishoemi/traffic-sim-v2/tree/main/.github/skills/using-agent-skills
Command: npx skills add https://github.com/raishoemi/traffic-sim-v2 --skill using-agent-skills-raishoemi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Engineering agents often start tasks without a defined process, leading to wrong assumptions, skipped verification, and scope creep. This meta-skill maps any incoming task to the correct workflow skill and enforces core operating behaviors across all of them. ## Core Features & Use Cases - Skill Discovery: A decision tree routes tasks by development phase (define, plan, build, verify, review, ship) to one of 23 workflow skills such as spec-driven-development, test-driven-development, or code-review-and-quality. - Core Operating Behaviors: Six non-negotiable rules apply across all skills: surface assumptions, manage confusion actively, push back when warranted, enforce simplicity, maintain scope discipline, and verify with evidence. - Lifecycle Sequencing: A canonical 16-step skill sequence covers a full feature lifecycle, while shorter chains handle bug fixes. - Use Case: When a session begins with a vague feature request, the agent uses this skill to route through interview-me, spec-driven-development, planning-and-task-breakdown, and incremental-implementation before writing code. ## Quick Start Ask the agent to identify which skill applies to your current task and follow that skill's workflow from start to verification.

Frequently Asked Questions about using-agent-skills

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I choose the right skill for a coding task?

Use the decision tree in this meta-skill: identify your development phase first, then follow the branch. For example, implementing code routes to incremental-implementation, while writing tests routes to test-driven-development.

What is the correct skill sequence for a new feature?

The canonical lifecycle runs interview-me, idea-refine, spec-driven-development, planning-and-task-breakdown, incremental-implementation, test-driven-development, code-review-and-quality, then git-workflow-and-versioning and shipping-and-launch. Not every step is mandatory for small changes.

Can multiple agent skills apply to one task?

Yes. Skills are composable workflows, and a single feature typically chains several in sequence, such as spec-driven-development followed by planning-and-task-breakdown and incremental-implementation.

When should I skip the spec-driven-development skill?

Skip it only for trivial, well-understood changes. The skill rules state that any non-trivial task without a spec should begin with spec-driven-development to avoid building on wrong assumptions.

What counts as verification before a task is complete?

Verification requires concrete evidence such as passing tests, build output, or runtime data. The definition-of-done reference sets the project-wide bar: tests pass, no regressions, behavior verified at runtime, and docs updated.