using-agent-skills

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

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

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 across the full development lifecycle, so the right process is followed from the start. ## Core Features & Use Cases - Skill Discovery Decision Tree: Routes tasks through a phase-based flowchart covering define, plan, build, verify, review, and ship stages. - 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 canonical skill order for complete features, from interview-me through shipping-and-launch. - Use Case: You receive 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 describing the work you are about to start.

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 your task belongs to, then 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.

What is the correct order of skills for building a complete 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. A feature implementation commonly chains several skills in sequence, such as spec-driven-development followed by planning, implementation, testing, review, and shipping skills.

What should I do when a task has no specification?

Start with spec-driven-development. The skill rules state that for any non-trivial task without a spec, defining requirements and acceptance criteria comes before writing code.

When is a task considered complete under these skills?

A task is complete only when verification passes with concrete evidence such as passing tests, build output, or runtime data. The project-wide Definition of Done applies to every change regardless of which skill is active.