skills.rest
MSC72m
MSC72mCOMMUNITY
Explore all skills by this author →
𝕏@MSC72mGitHub

using-agent-skills

Discovers and routes tasks to the appropriate engineering workflow skill.

Updated Aug 22, 2026
Search Tags:#AI agents#meta-skill#skill discovery#task orchestration#engineering workflow#workflow routing#development phases
One-click install
npx skills add https://github.com/MSC72m/DevForge --skill using-agent-skills-msc72m
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: using-agent-skills
Source: https://github.com/MSC72m/DevForge/tree/main/skills/using-agent-skills
Command: npx skills add https://github.com/MSC72m/DevForge --skill using-agent-skills-msc72m

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When starting a session or facing a new task, it is hard to know which engineering workflow skill applies. This meta-skill removes that guesswork by mapping each development phase to the correct skill and enforcing core operating behaviors across all of them. ## Core Features & Use Cases - Skill Discovery Flowchart: Routes any incoming task to the right skill, from interview-me and spec-driven-development through shipping-and-launch. - 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 16-step skill sequence for a complete feature and shorter sequences for tasks like bug fixes. - Use Case: A user asks to fix a broken login flow. The skill routes the work through debugging-and-error-recovery, then test-driven-development, then code-review-and-quality. ## 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 which agent skill to use for a task?▼

Identify the development phase of your task and follow the discovery flowchart. For example, new features route to spec-driven-development, while broken behavior routes to debugging-and-error-recovery.

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

The typical sequence runs from interview-me and spec-driven-development through planning, incremental implementation, test-driven-development, code review, and finally 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 idea-refine, spec-driven-development, planning-and-task-breakdown, incremental-implementation, and code-review-and-quality.

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

Skip it only for trivial tasks. If the work is non-trivial and no spec exists, the rules direct you to start with spec-driven-development before writing any code.

Why does the skill require verification before completing a task?▼

Verification prevents the failure mode of assuming code works because it looks right. Every skill includes a verification step requiring evidence such as passing tests, build output, or runtime data.

Related Skills

Explore More Software Engineering Skills→
BorisserzBorisserz
1

idea-refine

Refine raw ideas into actionable concepts through structured divergent and convergent thinking.

Community
Advanced
logo-solutionslogo-solutions

using-agent-skills

Route development tasks to matching engineering workflow skills via SKILL.md metadata.

Official
Advanced
heymishyheymishy

workflow

Diagnose stalled features and route the next pipeline action.

Community
Advanced
bnfergusonbnferguson

ask-matt

Routes a described situation to the matching skill or workflow in this repository.

Community
Intermediate