Agent skill
using-superpowers
Use at conversation start - establishes how to find and use skills, requiring skill loading before ANY response
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/using-superpowers-yairbederman-engineeringagency-dbfb2750
SKILL.md
Using Skills
The Rule
Load and apply relevant skills BEFORE any response or action. Even a 1% chance a skill might apply means you should check. If a skill turns out to be wrong for the situation, you don't need to use it.
How to Access Skills
Skills are located in global_workflows/skills/. Each skill folder contains a SKILL.md file with:
- YAML frontmatter:
nameanddescription - Detailed instructions for when and how to apply the skill
To use a skill:
- Read the
SKILL.mdfile - Announce: "Applying [skill-name] skill for [purpose]."
- Follow the skill instructions exactly
Mode-Based Auto-Loading
Skills are automatically applicable based on the current Engineering Agent mode:
| Agent Mode | Applicable Skills |
|---|---|
| ProductSpecReview | brainstorming |
| FeaturePlanning | brainstorming, writing-plans |
| TechSpec | writing-plans |
| TaskPlanning | writing-plans |
| Implementation | test-driven-development, executing-plans |
| BugFix | test-driven-development |
| CodeReview | requesting-code-review |
Common Rationalizations (Don't Fall For These)
| Rationalization | Reality |
|---|---|
| "I already know TDD" | Skills have specific checklists. Read them. |
| "This is quick, no skill needed" | Simple things become complex. Use the skill. |
| "I'll check the skill later" | Check BEFORE doing anything. |
| "The skill is overkill" | Discipline prevents mistakes. |
Skill Types
Rigid (TDD, debugging): Follow exactly. Don't adapt away discipline.
Flexible (brainstorming, writing-plans): Adapt principles to context.
The skill itself tells you which type it is.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
majiayu000/claude-skill-registry
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
majiayu000/claude-skill-registry
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
majiayu000/claude-skill-registry
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
majiayu000/claude-skill-registry
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
majiayu000/claude-skill-registry
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
majiayu000/claude-skill-registry
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?