using-agent-skills

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

Updated Jun 8, 2026
One-click install
npx skills add https://github.com/Avistian/nba --skill using-agent-skills-avistian
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: using-agent-skills
Source: https://github.com/Avistian/nba/tree/main/.cursor/skills/using-agent-skills
Command: npx skills add https://github.com/Avistian/nba --skill using-agent-skills-avistian

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 Decision Tree: Routes tasks by development phase (define, plan, build, verify, review, ship) to one of 23 specialized 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 before completion. - Lifecycle Sequencing: Defines the canonical skill order for full features, from interview-me through shipping-and-launch. - Use Case: When a user asks to implement a new API endpoint, the agent consults the decision tree, routes to api-and-interface-design and incremental-implementation, and follows each skill's verification steps. ## 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 the right skill for a development task?▼

Use the skill discovery decision tree: identify your development phase first, then follow the branch. For example, implementing code routes to incremental-implementation, while writing tests routes to test-driven-development.

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

The lifecycle sequence runs interview-me, idea-refine, spec-driven-development, planning-and-task-breakdown, incremental-implementation, test-driven-development, code-review-and-quality, then git-workflow-and-versioning and shipping-and-launch. Not every task needs every skill.

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, and code-review-and-quality, with each skill's steps followed in order.

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

Skip it only for trivial tasks with obvious requirements. The skill rules state that any non-trivial task without a spec should begin with spec-driven-development before any code is written.

What are the core operating behaviors all skills enforce?▼

Six behaviors apply across all skills: surface assumptions, manage confusion actively, push back when warranted, enforce simplicity, maintain scope discipline, and verify results with evidence rather than assuming correctness.