using-agent-skills

Discovers and routes tasks to the appropriate engineering workflow skill.

665|3|Updated Sep 12, 2026
One-click install
npx skills add https://github.com/rizqinrr/viserys-agent --skill using-agent-skills-rizqinrr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: using-agent-skills
Source: https://github.com/rizqinrr/viserys-agent/tree/main/skills/using-agent-skills
Command: npx skills add https://github.com/rizqinrr/viserys-agent --skill using-agent-skills-rizqinrr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI coding agents often improvise on every task, skipping specs, verification, and review steps. This meta-skill provides a consistent discovery and routing layer so the right engineering workflow skill is applied to each piece of work across the full development lifecycle. ## Core Features & Use Cases - Skill Discovery Decision Tree: Maps incoming tasks to the correct skill by development phase, from DEFINE through SHIP, covering 20+ workflow skills. - 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: Defines the canonical skill order for complete features and minimal sequences for smaller tasks like bug fixes. - Use Case: When a new feature request arrives with no spec, the decision tree routes you to interview-me, then spec-driven-development, then planning-and-task-breakdown before any code is written. ## Quick Start Ask the agent to identify which skill applies to your current task and follow that skill's workflow steps in order.

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 skill to use for a coding task?

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

What is the correct skill order for building a complete feature?

The typical sequence is interview-me, idea-refine, spec-driven-development, planning-and-task-breakdown, context-engineering, incremental-implementation, test-driven-development, code-review-and-quality, git-workflow-and-versioning, and shipping-and-launch. Not every task needs every skill.

Can multiple skills apply to a single task?

Yes, multiple skills can apply and often run in sequence. A bug fix might only need debugging-and-error-recovery, test-driven-development, and code-review-and-quality, while a full feature chains many more skills together.

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

Skip it only for trivial tasks where requirements are already unambiguous. For any non-trivial task without a spec, the rules direct you to start with spec-driven-development before writing code.

Why does the agent stop and ask questions instead of proceeding?

The confusion management behavior requires the agent to stop when it encounters inconsistencies or unclear requirements, name the specific confusion, and wait for resolution rather than guessing. This prevents wrong assumptions from becoming expensive rework.