Skip to content
cccskills
FreePublished on GitHub

using-superpowers

Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions

The English summary is being prepared. Showing the original description.

Trevoke/org-gtd.el486 stars(GitHub 486 + cccskills 0)

Run score Not tested

See how to install

Files included (1)

  • SKILL.md2.2 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

<EXTREMELY-IMPORTANT> If you think there is even a 1% chance a skill might apply to what you are doing, you ABSOLUTELY MUST read the skill.

IF A SKILL APPLIES TO YOUR TASK, YOU MUST USE IT.

This is not negotiable. This is not optional. You cannot rationalize your way out of this. </EXTREMELY-IMPORTANT>

Using Skills

The Rule

Check for skills BEFORE ANY RESPONSE. This includes clarifying questions. Even 1% chance means invoke the Skill tool first.

Development Workflow Skills

These skills form a pipeline. Each phase produces a dated artifact and references the next step:

SkillWhen to Use
/defineNew feature request, bug report, or requirement to break down
/architectRequirements exist, need technical design
/implementDesign exists, ready to build
/qaImplementation complete, need adversarial testing
/refactorCode quality pass after implementation

You don't always need all phases. Start at whichever phase makes sense.

Red Flags

These thoughts mean STOP — you're rationalizing:

ThoughtReality
"This is just a simple question"Questions are tasks. Check for skills.
"I need more context first"Skill check comes BEFORE clarifying questions.
"Let me explore the codebase first"Skills tell you HOW to explore. Check first.
"This doesn't need a formal skill"If a skill exists, use it.
"The skill is overkill"Simple things become complex. Use it.
"I'll just do this one thing first"Check BEFORE doing anything.

Skill Priority

When multiple skills could apply:

  1. Process skills first (define, architect) — determine HOW to approach
  2. Implementation skills second (implement, qa, refactor) — guide execution

Skill Types

Rigid (TDD, qa): Follow exactly. Don't adapt away discipline.

Flexible (patterns): Adapt principles to context.

The skill itself tells you which.

User Instructions

Instructions say WHAT, not HOW. "Add X" or "Fix Y" doesn't mean skip workflows.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Use when requirements exist and a technical design is needed before implementation begins

The English summary is being prepared. Showing the original description.

Trevoke/org-gtd.el486Updated Aug 7, 2026

define

Free

Use when a new feature request, bug report, or work request needs requirements defined before implementation

The English summary is being prepared. Showing the original description.

Trevoke/org-gtd.el486Updated Aug 7, 2026

Use when a design exists and it's time to break it into tasks and execute with subagent dispatch and review

The English summary is being prepared. Showing the original description.

Trevoke/org-gtd.el486Updated Aug 7, 2026

qa

Free

Use when implementation is complete and you want to verify quality through adversarial testing that writes code and provides evidence

The English summary is being prepared. Showing the original description.

Trevoke/org-gtd.el486Updated Aug 7, 2026

Use when code quality needs improvement after implementation, without changing behavior

The English summary is being prepared. Showing the original description.

Trevoke/org-gtd.el486Updated Aug 7, 2026

test

Free

Use EVERY TIME you need to run tests, verify tests pass, or check for regressions. ALWAYS use this instead of running eldev directly.

The English summary is being prepared. Showing the original description.

Trevoke/org-gtd.el486Updated Aug 7, 2026

See all skills by Trevoke

Report a problem with this skill