using-agent-skills

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

5|Updated Mar 5, 2024
One-click install
npx skills add https://github.com/TRAPZZY/God-Eyes --skill using-agent-skills-trapzzy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: using-agent-skills
Source: https://github.com/TRAPZZY/God-Eyes/tree/main/.skills/using-agent-skills
Command: npx skills add https://github.com/TRAPZZY/God-Eyes --skill using-agent-skills-trapzzy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Engineering tasks often fail because the wrong process is applied or no process is applied at all. This meta-skill ensures every incoming task is matched to the correct workflow skill before work begins, preventing skipped verification, wrong assumptions, and scope creep. ## Core Features & Use Cases - Skill Discovery: Maps incoming tasks to the right skill via a decision tree covering define, plan, build, verify, review, and ship phases. - Core Operating Behaviors: Enforces six non-negotiable behaviors including surfacing assumptions, managing confusion, pushing back on bad ideas, and verifying results. - Lifecycle Sequencing: Defines the typical skill chain from idea-refine through shipping-and-launch for complete features. - Use Case: When a vague feature request arrives, use this skill to route it through idea-refine, spec-driven-development, and planning-and-task-breakdown before any code is written. ## 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 go to 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 typical sequence is 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, then shipping-and-launch.

Can multiple agent skills apply to one task?▼

Yes, multiple skills can apply in sequence. A feature implementation typically chains skills from definition through shipping, while a bug fix may only need debugging-and-error-recovery, test-driven-development, and code-review-and-quality.

When should I skip using a workflow skill?▼

Not every task needs every skill, but you should always check for an applicable skill before starting work. Trivial tasks may need none, while any non-trivial task without a spec should begin with spec-driven-development.

Why does the skill require surfacing assumptions before implementation?▼

Silently filling ambiguous requirements is the most common failure mode in engineering work. Stating assumptions explicitly lets humans correct misunderstandings early, which is cheaper than rework after implementation.