using-agent-skills

Discovers and routes tasks to the appropriate engineering workflow skill.

Updated Sep 5, 2026
One-click install
npx skills add https://github.com/pohlai88/afenda-xforge-v5 --skill using-agent-skills-pohlai88
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: using-agent-skills
Source: https://github.com/pohlai88/afenda-xforge-v5/tree/main/.agents/skills/using-agent-skills
Command: npx skills add https://github.com/pohlai88/afenda-xforge-v5 --skill using-agent-skills-pohlai88

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When starting a development task, it is often unclear which engineering workflow applies, leading to skipped specs, missing verification, and inconsistent quality. This meta-skill maps any incoming task to the correct skill across the full development lifecycle. ## Core Features & Use Cases - Skill Discovery: A decision tree routes tasks by development phase (define, plan, build, verify, review, ship) to one of 23 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 flawed approaches, and verifying results. - Lifecycle Sequencing: Defines the canonical skill order for complete features, from interview-me through shipping-and-launch. - Use Case: A developer receives a vague feature request; the skill routes them to interview-me, then spec-driven-development, then incremental-implementation, ensuring each phase follows a verified process. ## Quick Start Ask the agent to identify 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 skill for a development task?

Identify the development phase your task belongs to, then follow the decision tree: vague ideas route to interview-me or idea-refine, new features to spec-driven-development, implementation to incremental-implementation, and bugs to debugging-and-error-recovery.

What is the correct order of skills for building a 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, then git-workflow-and-versioning and shipping-and-launch.

Can multiple skills apply to a single task?

Yes, multiple skills can apply in sequence. A feature implementation might chain spec-driven-development, planning-and-task-breakdown, incremental-implementation, test-driven-development, and code-review-and-quality, while a bug fix may only need debugging and testing skills.

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

Only trivial tasks with unambiguous requirements can skip it. The skill rules state that when in doubt on any non-trivial task without a spec, you should begin with spec-driven-development before writing code.

What verification is required before a task is complete?

Every skill includes a verification step requiring concrete evidence such as passing tests, build output, or runtime data. The project-wide Definition of Done requires tests passing, no regressions, runtime verification, and updated documentation.