using-agent-skills

Discovers and routes tasks to the appropriate engineering workflow skill.

Updated Aug 15, 2026
One-click install
npx skills add https://github.com/jacksonlee-tw/mystock-vue --skill using-agent-skills-jacksonlee-tw
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: using-agent-skills
Source: https://github.com/jacksonlee-tw/mystock-vue/tree/main/mystock-vue/.agents/skills/using-agent-skills
Command: npx skills add https://github.com/jacksonlee-tw/mystock-vue --skill using-agent-skills-jacksonlee-tw

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When starting a development task, it is hard to know which engineering workflow skill applies. This meta-skill provides a decision tree and lifecycle sequence that maps any task to the correct skill, while enforcing core operating behaviors like surfacing assumptions and verifying results. ## Core Features & Use Cases - Skill Discovery Decision Tree: Maps incoming tasks to the right skill by development phase, from interview-me through shipping-and-launch. - Core Operating Behaviors: Enforces six non-negotiable behaviors including surfacing assumptions, managing confusion, pushing back on bad ideas, and verifying outcomes. - Lifecycle Sequencing: Defines the typical 16-step skill sequence for a complete feature and shorter sequences for tasks like bug fixes. - Use Case: You receive a vague feature request. The decision tree routes you to interview-me, then spec-driven-development, then incremental-implementation, ensuring each phase follows a proven process. ## Quick Start Ask the agent to identify 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 which agent skill to use for a task?▼

Use the decision tree in this meta-skill: identify your development phase (define, plan, build, verify, review, ship) and follow the branch matching your situation. For example, UI work routes to frontend-ui-engineering, while a broken feature routes to debugging-and-error-recovery.

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

The typical lifecycle runs interview-me, idea-refine, spec-driven-development, planning-and-task-breakdown, incremental-implementation, test-driven-development, code-review-and-quality, then shipping-and-launch. Not every task needs every skill; a bug fix may only need debugging, testing, and review.

Can multiple agent skills apply to one task?▼

Yes, multiple skills can apply in sequence. A feature implementation might chain spec-driven-development, planning-and-task-breakdown, incremental-implementation, test-driven-development, and code-review-and-quality, with observability-and-instrumentation running in parallel during the build.

When should I skip using a skill workflow?▼

Skills are workflows, not suggestions, so check for an applicable skill before starting any non-trivial work. Trivial changes may not need the full lifecycle, but verification against the Definition of Done applies to every change regardless of which skill is active.

What should I do when requirements are unclear or conflicting?▼

Stop and do not proceed with a guess. Name the specific confusion, present the tradeoff or ask the clarifying question, and wait for resolution. Silently picking one interpretation is listed as a core failure mode.