using-agent-skills

Discovers and routes tasks to the appropriate engineering workflow skill by development phase.

1|Updated May 29, 2026
One-click install
npx skills add https://github.com/memasanz/agent-harness --skill using-agent-skills-memasanz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: using-agent-skills
Source: https://github.com/memasanz/agent-harness/tree/main/.github/skills/using-agent-skills
Command: npx skills add https://github.com/memasanz/agent-harness --skill using-agent-skills-memasanz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When working with a large library of agent skills, it is hard to know which skill applies to the current task and in what order to apply them. This meta-skill provides a decision tree, lifecycle sequence, and core operating behaviors so the right workflow skill is invoked at the right time. ## Core Features & Use Cases - Skill Discovery Decision Tree: Maps incoming tasks (new feature, bug fix, code review, deployment) to the correct phase-specific skill such as spec-driven-development or debugging-and-error-recovery. - Core Operating Behaviors: Enforces six non-negotiable behaviors across all skills, including surfacing assumptions, managing confusion, pushing back on flawed approaches, and verifying results. - Lifecycle Sequencing: Defines the full feature lifecycle from interview-me through shipping-and-launch, plus trimmed sequences for smaller tasks like bug fixes. - Use Case: You start a session with a vague feature request. The decision tree routes you to interview-me, then spec-driven-development, then incremental-implementation, ensuring each phase locks its decisions before the next begins. ## Quick Start Ask the agent to identify which skill applies to your current task and follow that skill's workflow from start to verification.

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?

Identify the development phase your task belongs to, then follow the decision tree: new features route to spec-driven-development, broken behavior routes to debugging-and-error-recovery, and reviews route to code-review-and-quality. When in doubt on non-trivial work, start with a spec.

What is a meta-skill in an agent skills library?

A meta-skill governs how all other skills are discovered and invoked. It defines the routing logic, the order in which skills chain together, and the shared operating behaviors that apply across every skill in the collection.

Can multiple agent skills apply to one task?

Yes. A full feature typically chains interview-me, spec-driven-development, planning-and-task-breakdown, incremental-implementation, test-driven-development, code-review-and-quality, and shipping-and-launch in sequence. Smaller tasks use shorter chains.

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

Skip it only for trivial tasks with unambiguous requirements. A bug fix may only need debugging-and-error-recovery, test-driven-development, and code-review-and-quality. Non-trivial work without a spec should always start with spec-driven-development.

Why does the skill require surfacing assumptions before coding?

The most common failure mode is making wrong assumptions and running with them unchecked. Stating assumptions explicitly before implementation lets the human correct misunderstandings early, which is cheaper than rework after verification fails.