addy-using-agent-skills

Discovers and routes tasks to the appropriate engineering workflow skill.

Updated Aug 21, 2026
One-click install
npx skills add https://github.com/TylerSimons1127/vibe --skill addy-using-agent-skills-tylersimons1127
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: addy-using-agent-skills
Source: https://github.com/TylerSimons1127/vibe/tree/main/skills/addy-using-agent-skills
Command: npx skills add https://github.com/TylerSimons1127/vibe --skill addy-using-agent-skills-tylersimons1127

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

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 maps incoming tasks to the correct skill by development phase, so the right process is followed instead of improvising. ## Core Features & Use Cases - Skill Discovery: A decision tree routes tasks by 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: Enforces six non-negotiable behaviors across all skills, including surfacing assumptions, managing confusion, pushing back on bad ideas, and verifying results. - Lifecycle Sequencing: Defines the typical skill order for a complete feature, from interview-me through shipping-and-launch, plus a standing Definition of Done checklist. - Use Case: A bug report arrives mid-session; the routing tree directs you to debugging-and-error-recovery, then test-driven-development, then code-review-and-quality. ## Quick Start Ask the agent to identify which skill applies to your current task before starting any implementation work.

Frequently Asked Questions about addy-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 of the task first, then follow the decision tree: new features go to spec-driven-development, implementation goes to incremental-implementation, and broken behavior goes to debugging-and-error-recovery. Multiple skills can apply in sequence.

What is a meta-skill for agent skill discovery?▼

A meta-skill governs how all other skills are discovered and invoked. This one maps tasks to workflow skills by phase and enforces shared operating behaviors like surfacing assumptions and verifying results before declaring work done.

Can multiple workflow skills apply to one feature?▼

Yes. A complete feature typically chains skills in order: interview-me, spec-driven-development, planning-and-task-breakdown, incremental-implementation, test-driven-development, code-review-and-quality, and shipping-and-launch. A bug fix needs only a subset.

What is the difference between Definition of Done and acceptance criteria?▼

Acceptance criteria are specific to one task and answer whether the right thing was built. The Definition of Done is a fixed project-wide checklist covering correctness, quality, integration, documentation, and ship-readiness that every change must pass.

When should I skip using a workflow skill?▼

Skills should be checked before starting any work, since they encode processes that prevent common mistakes. Trivial tasks may not need the full lifecycle, but verification steps within any active skill should never be skipped.