using-agent-skills

Discovers and routes tasks to phase-appropriate engineering workflow skills.

Updated Sep 5, 2026
One-click install
npx skills add https://github.com/nntoan/ultra-omp --skill using-agent-skills-nntoan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: using-agent-skills
Source: https://github.com/nntoan/ultra-omp/tree/main/packages/proflow/skills/using-agent-skills
Command: npx skills add https://github.com/nntoan/ultra-omp --skill using-agent-skills-nntoan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Engineers often start tasks without a defined process, leading to wrong assumptions, scope creep, skipped verification, and overcomplicated code. This meta-skill solves that by mapping any incoming task to the correct engineering workflow skill and enforcing core operating behaviors across all of them. ## Core Features & Use Cases - Skill Discovery Flowchart: Routes tasks by development phase (define, plan, build, verify, review, ship) to one of 20+ specialized skills such as spec-driven-development, test-driven-development, or debugging-and-error-recovery. - Core Operating Behaviors: Enforces six non-negotiable behaviors including surfacing assumptions, managing confusion, pushing back on bad ideas, enforcing simplicity, maintaining scope discipline, and verifying results. - Lifecycle Sequencing: Provides a canonical 16-step skill sequence for full features and trimmed sequences for smaller tasks like bug fixes. - Use Case: When a user asks to implement a new API endpoint, the skill routes through spec-driven-development, planning-and-task-breakdown, incremental-implementation, and test-driven-development in order. ## Quick Start Ask the agent to identify which engineering workflow 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 engineering workflow skill for a task?▼

Identify the development phase your task belongs to, then follow the discovery flowchart. New features route to spec-driven-development, bugs route to debugging-and-error-recovery, and code reviews route to code-review-and-quality.

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, then 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, and test-driven-development, while a bug fix may only need three skills.

When should I skip spec-driven-development?▼

Skip it only for trivial tasks with unambiguous requirements. The skill rules state that when in doubt on any non-trivial task without a spec, you should start with spec-driven-development before writing code.

What counts as verification before a task is complete?▼

Verification requires concrete evidence such as passing tests, build output, or runtime data, never just visual inspection. Every change must also meet the project-wide definition of done covering tests, regressions, and documentation.