using-agent-skills

Discovers and routes tasks to the appropriate engineering workflow skill.

1|Updated Jul 5, 2026
One-click install
npx skills add https://github.com/yersonargotev/packy --skill using-agent-skills-yersonargotev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: using-agent-skills
Source: https://github.com/yersonargotev/packy/tree/main/bundle/skills/using-agent-skills
Command: npx skills add https://github.com/yersonargotev/packy --skill using-agent-skills-yersonargotev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Engineering agents often start work without a defined process, leading to wrong assumptions, skipped verification, and scope creep. This meta-skill maps any incoming task to the correct workflow 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, test-driven-development, and code-review-and-quality. - Core Operating Behaviors: Six non-negotiable rules apply at all times: surface assumptions, manage confusion actively, push back when warranted, enforce simplicity, maintain scope discipline, and verify with evidence. - Lifecycle Sequencing: Defines the typical skill chain for a complete feature, from interview-me through shipping-and-launch, plus a standing Definition of Done checklist in references/definition-of-done.md. - Use Case: A user asks to fix a production bug. The skill routes to debugging-and-error-recovery, then test-driven-development, then code-review-and-quality, ensuring reproduction, a failing test, and review before the fix ships. ## Quick Start Ask the agent to determine which 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 skill for a coding task?▼

Identify the development phase of your task and 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. When in doubt on non-trivial work, start with spec-driven-development.

What is a meta-skill for agent workflows?▼

A meta-skill governs how other skills are discovered and invoked rather than performing a task itself. This one maps tasks to phase-specific skills and defines six core operating behaviors, like surfacing assumptions and verifying with evidence, that apply across all skills.

Can multiple workflow skills apply to one feature?▼

Yes, skills chain in sequence. A complete feature typically runs 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 task-specific 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 need no skill, but skipping verification steps within an active skill is never acceptable.