using-agent-skills

Routes incoming tasks to the appropriate engineering workflow skill by development phase.

1|Updated Sep 4, 2026
One-click install
npx skills add https://github.com/SanHsien/agent-skills --skill using-agent-skills-sanhsien
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: using-agent-skills
Source: https://github.com/SanHsien/agent-skills/tree/main/skills/using-agent-skills
Command: npx skills add https://github.com/SanHsien/agent-skills --skill using-agent-skills-sanhsien

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When working with a large library of agent skills, it is hard to know which workflow applies to the task at hand. This meta-skill acts as the entry point that maps any incoming task to the right skill, and enforces core operating behaviors like surfacing assumptions and verifying results. ## Core Features & Use Cases - Skill Discovery: A decision tree routes tasks by development phase (define, plan, build, verify, review, ship) to one of 20+ workflow skills such as spec-driven-development or test-driven-development. - Core Operating Behaviors: Six non-negotiable rules apply across all skills, including surfacing assumptions, managing confusion, pushing back on bad ideas, enforcing simplicity, maintaining scope discipline, and verifying with evidence. - Lifecycle Sequencing: Defines the typical skill order for a complete feature, from interview-me through shipping-and-launch, plus a quick-reference table of every skill. - Use Case: At the start of a session you describe a new feature; the meta-skill routes you to spec-driven-development first, then planning-and-task-breakdown, then incremental-implementation with test-driven-development. ## Quick Start Ask the agent to determine which skill applies to your current task, for example by describing the work you are about to start and letting it route you to the right workflow.

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 which agent skill to use for a task?

Identify the development phase of your task and follow the decision tree: new features route to spec-driven-development, implementation to incremental-implementation, testing to test-driven-development, and deployment to shipping-and-launch. When in doubt, start with a spec.

What is the correct order of skills for building a feature?

The typical lifecycle runs interview-me, idea-refine, spec-driven-development, planning-and-task-breakdown, incremental-implementation, test-driven-development, code-review-and-quality, and shipping-and-launch. Not every task needs every skill; a bug fix may only need debugging, testing, and review.

Can multiple agent skills apply to one task?

Yes, multiple skills can apply and often run in sequence. A feature implementation might chain spec-driven-development, planning-and-task-breakdown, incremental-implementation, test-driven-development, and code-review-and-quality.

When should I skip the spec and start coding directly?

The skill rules state that non-trivial tasks without a spec should begin with spec-driven-development. Building without a spec because requirements seem obvious is listed as a failure mode to avoid.

What operating behaviors apply across all skills?

Six behaviors apply at all times: surface assumptions, manage confusion actively, push back when warranted, enforce simplicity, maintain scope discipline, and verify with evidence rather than assuming correctness.