using-agent-skills

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

Updated Jun 13, 2026
One-click install
npx skills add https://github.com/22Teikk/22Teikk-Agent-Skills-Hub --skill using-agent-skills-22teikk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: using-agent-skills
Source: https://github.com/22Teikk/22Teikk-Agent-Skills-Hub/tree/main/core/skills/using-agent-skills
Command: npx skills add https://github.com/22Teikk/22Teikk-Agent-Skills-Hub --skill using-agent-skills-22teikk

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. This meta-skill maps incoming tasks to the correct engineering workflow skill across the Define, Plan, Build, Verify, Review, and Ship phases, and enforces core operating behaviors like surfacing assumptions and verifying results. ## Core Features & Use Cases - Skill Discovery: A decision tree routes any task (new feature, bug fix, code review, deployment) to the matching skill such as spec-driven-development, test-driven-development, or code-review-and-quality. - Core Operating Behaviors: Enforces six non-negotiable behaviors across all skills, including surfacing assumptions, managing confusion, pushing back on bad ideas, and verifying with evidence. - Lifecycle Sequencing: Defines the full feature lifecycle order from interview-me through shipping-and-launch, plus a quick-reference table of all 28 skills by phase. - Use Case: At the start of a session you describe a new Android feature; the skill routes you through spec-driven-development, planning-and-task-breakdown, incremental-implementation, and test-driven-development in sequence. ## Quick Start Ask the agent to identify which skill applies to your current task, for example by describing that you have a finished spec and need to break it into verifiable tasks.

Frequently Asked Questions about using-agent-skills

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I know which agent skill to use for my task?▼

Identify your development phase first, then follow the decision tree: new features route to spec-driven-development, implementation to incremental-implementation, testing to test-driven-development, and reviews to code-review-and-quality. When in doubt on non-trivial tasks, start with a spec.

What is the correct order of skills for a complete 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, code-simplification, then git-workflow-and-versioning and shipping-and-launch. Smaller tasks like bug fixes only need debugging-and-error-recovery, test-driven-development, and code review.

Can multiple agent skills apply to one task?▼

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

Does this skill support Android development workflows?▼

Yes, the routing tree includes Android-specific skills for Kotlin and Java UI work, data and concurrency, dependency injection and build, testing and benchmarking, and Maestro-based E2E testing. These sit under the Build and Verify phases.

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

Skip it only for trivial tasks where requirements are unambiguous. The skill rules state that any non-trivial task without a spec should begin with spec-driven-development, since building without a spec is a listed failure mode.