using-agent-skills

Discovers and routes tasks to the appropriate engineering workflow skill by development phase.

Updated Sep 15, 2026
One-click install
npx skills add https://github.com/Qiuyi-Hong/addyosmani-skills --skill using-agent-skills-qiuyi-hong
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: using-agent-skills
Source: https://github.com/Qiuyi-Hong/addyosmani-skills/tree/main/skills/using-agent-skills
Command: npx skills add https://github.com/Qiuyi-Hong/addyosmani-skills --skill using-agent-skills-qiuyi-hong

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 maps any incoming task to the correct skill based on its development phase, so the right process is followed every time. ## Core Features & Use Cases - Phase-Based Skill Discovery: A decision tree routes tasks across Define, Plan, Build, Verify, Review, and Ship phases to one of 23 skills such as spec-driven-development or test-driven-development. - Core Operating Behaviors: Enforces six non-negotiable behaviors including surfacing assumptions, managing confusion, pushing back on bad ideas, and verifying results. - Lifecycle Sequencing: Defines the typical skill order for a complete feature, from interview-me through shipping-and-launch. - Use Case: You start a session with a vague feature request. The skill routes you to interview-me, then spec-driven-development, then planning-and-task-breakdown, ensuring no phase is skipped. ## Quick Start Ask the agent to determine which skill applies to your current task, for example by saying you have a spec and need to break it into tasks.

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 using the decision tree: unclear requirements route to interview-me, a spec needing tasks routes to planning-and-task-breakdown, and code implementation routes to incremental-implementation. The tree covers all 23 skills.

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

The typical sequence is 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.

Can multiple agent skills apply to one task?

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

Do I need a skill for a small bug fix?

A bug fix typically only needs debugging-and-error-recovery, test-driven-development, and code-review-and-quality. The full lifecycle sequence is reserved for complete features.

What should I do when requirements are unclear or conflicting?

Stop and name the specific confusion rather than guessing. Present the tradeoff or ask a clarifying question, and wait for resolution before continuing with implementation.