using-agent-skills

Discovers and routes tasks to phase-specific engineering workflow skills.

Updated Jun 23, 2026
One-click install
npx skills add https://github.com/jampissarandev/Expense-Tracker --skill using-agent-skills-jampissarandev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: using-agent-skills
Source: https://github.com/jampissarandev/Expense-Tracker/tree/main/.github/skills/using-agent-skills
Command: npx skills add https://github.com/jampissarandev/Expense-Tracker --skill using-agent-skills-jampissarandev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Engineering agents often start tasks without a defined process, leading to wrong assumptions, skipped verification, and scope creep. This meta-skill provides a discovery layer that maps any incoming task to the correct workflow skill and enforces core operating behaviors across all of them. ## Core Features & Use Cases - Skill Discovery Flowchart: Routes tasks by development phase (define, plan, build, verify, review, ship) to one of 20+ specialized skills such as spec-driven-development, test-driven-development, or debugging-and-error-recovery. - Core Operating Behaviors: Enforces six non-negotiable rules including surfacing assumptions, managing confusion actively, pushing back on flawed approaches, and verifying results with evidence. - Lifecycle Sequencing: Defines the typical skill chain for a complete feature, from interview-me through shipping-and-launch, plus trimmed sequences for smaller tasks like bug fixes. - Use Case: When a user asks to implement a new API endpoint, the agent consults this skill, routes to api-and-interface-design and incremental-implementation, and applies the verification and scope-discipline rules throughout. ## 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 agent skill for a development task?

Identify the development phase of your task and follow the discovery flowchart: new features route to spec-driven-development, implementation to incremental-implementation, bugs to debugging-and-error-recovery, and reviews to code-review-and-quality.

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

A meta-skill governs how all other skills are discovered and invoked. It contains the routing logic, core operating behaviors, and lifecycle sequences rather than a task-specific workflow of its own.

Can multiple agent skills apply to one task?

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

When should I skip the full skill lifecycle?

Small tasks need only a subset. A bug fix typically requires just debugging-and-error-recovery, test-driven-development, and code-review-and-quality rather than the full sixteen-step sequence.

Why does the skill require surfacing assumptions before coding?

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