using-agent-skills

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

Updated Jul 10, 2026
One-click install
npx skills add https://github.com/CodeCrafterAdi2006/Ink-and-Code --skill using-agent-skills-codecrafteradi2006
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: using-agent-skills
Source: https://github.com/CodeCrafterAdi2006/Ink-and-Code/tree/main/Skills/using-agent-skills
Command: npx skills add https://github.com/CodeCrafterAdi2006/Ink-and-Code --skill using-agent-skills-codecrafteradi2006

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Engineering agents often start tasks without a defined process, leading to wrong assumptions, skipped verification, scope creep, and overcomplicated code. This meta-skill provides a discovery layer that maps any incoming task to the correct phase-specific workflow skill and enforces core operating behaviors across all of them. ## Core Features & Use Cases - Skill Discovery Tree: A decision flowchart routes tasks by development phase (define, plan, build, verify, review, ship) to one of 23 specialized skills such as spec-driven-development, test-driven-development, or debugging-and-error-recovery. - Core Operating Behaviors: Six non-negotiable rules apply across all skills: surface assumptions, manage confusion actively, push back when warranted, enforce simplicity, maintain scope discipline, and verify with evidence. - Lifecycle Sequencing: Defines the canonical skill order for a full feature (interview-me through shipping-and-launch) and minimal sequences for smaller tasks like bug fixes. - Use Case: A user asks an agent to fix a broken API endpoint. The meta-skill routes the task to debugging-and-error-recovery, then test-driven-development, then code-review-and-quality, ensuring reproduction, a failing test, and review before completion. ## Quick Start Ask the agent to determine which engineering 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 agent skill for a coding task?

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

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

The lifecycle sequence runs interview-me, idea-refine, spec-driven-development, planning-and-task-breakdown, context-engineering, incremental-implementation, test-driven-development, code-review-and-quality, git-workflow-and-versioning, documentation-and-adrs, and shipping-and-launch.

Can multiple agent skills apply to a single task?

Yes, skills compose in sequence. A bug fix typically needs only debugging-and-error-recovery, test-driven-development, and code-review-and-quality, while a full feature may chain eight or more skills across phases.

When should I skip spec-driven-development?

Only trivial tasks skip the spec step. The skill rules state that any non-trivial task without a spec should begin with spec-driven-development, since building without defined acceptance criteria is a listed failure mode.

What counts as verification before a task is complete?

Verification requires concrete evidence such as passing tests, build output, or runtime data, never assumptions that something seems right. Each skill has a local verification step, and the project-wide Definition of Done requires passing tests, no regressions, and updated docs.