using-agent-skills

Discovers and routes tasks to the appropriate engineering workflow skill.

1|Updated Mar 2, 2025
One-click install
npx skills add https://github.com/marjorg/setup --skill using-agent-skills-marjorg
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: using-agent-skills
Source: https://github.com/marjorg/setup/tree/main/home/.agents/skills/using-agent-skills
Command: npx skills add https://github.com/marjorg/setup --skill using-agent-skills-marjorg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When starting a development task, it is hard to know which engineering workflow or process applies. This meta-skill maps any incoming task to the right skill across the full software lifecycle, from requirements to launch, and enforces core operating behaviors like surfacing assumptions and verifying results. ## Core Features & Use Cases - Skill Discovery 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: Enforces six non-negotiable behaviors including surfacing assumptions, managing confusion, pushing back on bad ideas, and verifying outcomes. - Lifecycle Sequencing: Provides a canonical 16-step skill sequence for complete features and trimmed sequences for smaller tasks like bug fixes. - Use Case: You receive a vague feature request. The skill routes you to interview-me, then spec-driven-development, then planning-and-task-breakdown before any code is written. ## 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 engineering workflow skill to use for a task?▼

Identify the development phase of your task and follow the decision tree: unclear requirements route to interview-me, new features to spec-driven-development, implementation to incremental-implementation, and failures to debugging-and-error-recovery.

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

The lifecycle sequence runs from interview-me and spec-driven-development through planning, incremental implementation, test-driven-development, code review, and finally shipping-and-launch. Smaller tasks use only a subset of this chain.

Can multiple agent skills apply to a single task?▼

Yes, multiple skills can apply in sequence. A feature might chain idea-refine, spec-driven-development, planning-and-task-breakdown, incremental-implementation, test-driven-development, and code-review-and-quality.

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

Skip it only for trivial tasks with obvious requirements. For any non-trivial task without a written spec, the rules direct you to start with spec-driven-development before writing code.

What should I do when requirements conflict with existing code?▼

Stop and name the specific confusion instead of guessing. Present the tradeoff or ask which source takes precedence, then wait for resolution before continuing implementation.