using-agent-skills

Discovers and routes tasks to the appropriate engineering workflow skill.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/QT-7274/dotfiles --skill using-agent-skills-qt-7274
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: using-agent-skills
Source: https://github.com/QT-7274/dotfiles/tree/main/using-agent-skills
Command: npx skills add https://github.com/QT-7274/dotfiles --skill using-agent-skills-qt-7274

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When starting a development task, it is hard to know which engineering workflow applies, and skipping structured processes leads to wrong assumptions, scope creep, and unverified code. This meta-skill maps any incoming task to the correct skill across the full development lifecycle. ## 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: Enforces six non-negotiable behaviors including surfacing assumptions, managing confusion, pushing back on bad ideas, and verifying results with evidence. - Lifecycle Sequencing: Provides a canonical 16-step skill sequence for complete features and trimmed sequences for smaller tasks like bug fixes. - Use Case: You receive a vague feature request. The routing tree directs you to interview-me, then spec-driven-development, then planning-and-task-breakdown before any code is written. ## Quick Start Ask the agent to determine which skill applies to your current task before starting any implementation work.

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 development task?▼

Identify the development phase your task belongs to, then follow the decision tree: vague ideas route to interview-me, new features to spec-driven-development, implementation to incremental-implementation, and bugs to debugging-and-error-recovery.

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

The typical sequence runs interview-me, idea-refine, spec-driven-development, planning-and-task-breakdown, incremental-implementation, test-driven-development, code-review-and-quality, then shipping-and-launch. Not every task needs every skill.

Can multiple skills apply to a single task?▼

Yes, multiple skills can apply in sequence. A feature implementation might chain spec-driven-development through planning, implementation, testing, review, simplification, and launch skills.

When should I skip using a skill workflow?▼

Skills are workflows, not suggestions, so an applicable skill should be checked before starting any work. Small bug fixes may only need debugging-and-error-recovery, test-driven-development, and code-review-and-quality.

Why does the skill require surfacing assumptions before coding?▼

The most common failure mode is making wrong assumptions and running with them unchecked. Stating assumptions explicitly before non-trivial work lets the human correct misunderstandings early, which is cheaper than rework.