using-agent-skills

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

Updated Apr 28, 2026
One-click install
npx skills add https://github.com/JacobThree/zero-bloat-mcp-stack --skill using-agent-skills-jacobthree
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: using-agent-skills
Source: https://github.com/JacobThree/zero-bloat-mcp-stack/tree/main/ai_blueprints/agent-skills/skills/using-agent-skills
Command: npx skills add https://github.com/JacobThree/zero-bloat-mcp-stack --skill using-agent-skills-jacobthree

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Engineering tasks often fail because AI assistants skip structured processes, make unchecked assumptions, or overcomplicate solutions. This meta-skill solves that by acting as a router that identifies the development phase of any incoming task and directs the AI to the correct workflow skill, while enforcing core operating behaviors like surfacing assumptions and verifying results. ## Core Features & Use Cases - Skill Discovery and Routing: Maps incoming tasks to one of 18 phase-specific skills (define, plan, build, verify, review, ship) using a decision tree covering everything from idea refinement to deployment. - Core Operating Behaviors: Enforces six non-negotiable behaviors across all skills, including surfacing assumptions, managing confusion, pushing back on bad approaches, enforcing simplicity, maintaining scope discipline, and verifying outcomes. - Lifecycle Sequencing: Defines the full feature lifecycle from idea-refine through shipping-and-launch, with guidance on which subsets apply to smaller tasks like bug fixes. - Use Case: When a user asks to build a new feature, the skill routes the session through spec-driven-development, planning-and-task-breakdown, incremental-implementation, and test-driven-development in sequence rather than jumping straight to code. ## Quick Start Ask the assistant to determine which agent skill applies to your current task, such as routing a vague feature idea through idea refinement and specification before writing any code.

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 agent skill for my task?▼

Identify your development phase first, then follow the decision tree: vague ideas go to idea-refine, new features to spec-driven-development, implementation to incremental-implementation, and bugs to debugging-and-error-recovery. When in doubt on non-trivial tasks, start with spec-driven-development.

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

The full lifecycle runs idea-refine, spec-driven-development, planning-and-task-breakdown, context-engineering, source-driven-development, incremental-implementation, test-driven-development, code-review-and-quality, git-workflow-and-versioning, documentation-and-adrs, then shipping-and-launch. Smaller tasks use only the relevant subset.

Can multiple agent skills apply to a single task?▼

Yes, multiple skills can apply and often run in sequence. A feature implementation might chain spec-driven-development, planning-and-task-breakdown, incremental-implementation, test-driven-development, and code-review-and-quality, while a bug fix may only need debugging, testing, and review.

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

Skip it only for trivial tasks where requirements are unambiguous. The skill rules state that if a task is non-trivial and has no spec, you should begin with spec-driven-development rather than building on assumptions.

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 concrete evidence such as passing tests, build output, or runtime data before a task counts as complete.