using-agent-skills

Discovers and routes tasks to the appropriate engineering workflow skill.

Updated May 13, 2026
One-click install
npx skills add https://github.com/sapatamuku-creator/mastersapatamuku --skill using-agent-skills-sapatamuku-creator
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: using-agent-skills
Source: https://github.com/sapatamuku-creator/mastersapatamuku/tree/main/releases/v2.7/.agents/skills/using-agent-skills
Command: npx skills add https://github.com/sapatamuku-creator/mastersapatamuku --skill using-agent-skills-sapatamuku-creator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When working on software tasks, it is hard to know which engineering workflow applies at each stage, and skipping proven processes leads to wrong assumptions, scope creep, and unverified code. This meta-skill maps any incoming task to the correct skill and enforces core operating behaviors across all of them. ## 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: Six non-negotiable rules apply at all times, including surfacing assumptions, managing confusion, pushing back on bad ideas, enforcing simplicity, maintaining scope discipline, and verifying results. - Lifecycle Sequencing: A canonical 16-step skill sequence shows how skills chain together for a complete feature, from interview-me through shipping-and-launch. - Use Case: You receive a vague feature request. The routing tree directs you to interview-me first, then spec-driven-development, then incremental-implementation, ensuring each phase follows a verified process. ## Quick Start Ask the agent to identify which skill applies to your current task and follow that skill's workflow from start to verification.

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 coding 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, bugs to debugging-and-error-recovery, and reviews to code-review-and-quality.

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

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

Can multiple skills apply to one task?▼

Yes, multiple skills can apply and often chain in sequence. A feature implementation might flow from spec-driven-development through planning, implementation, testing, review, and shipping skills.

When should I skip using a skill workflow?▼

Skills should be checked before starting any work since they encode processes that prevent common mistakes. Simple bug fixes may only need debugging-and-error-recovery, test-driven-development, and code-review-and-quality rather than the full lifecycle.

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 before a task counts as complete.