mirror of
https://github.com/obra/superpowers.git
synced 2026-04-24 18:49:07 +08:00
Compare commits
7 Commits
gs/plan-mo
...
feat/codex
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
6e95f8dbdb | ||
|
|
5b3263d725 | ||
|
|
6023d5e74b | ||
|
|
a6f3dd1614 | ||
|
|
a171953947 | ||
|
|
c60991457a | ||
|
|
c8ede5e5c5 |
@@ -81,7 +81,6 @@ These thoughts mean STOP—you're rationalizing:
|
||||
| "I'll just do this one thing first" | Check BEFORE doing anything. |
|
||||
| "This feels productive" | Undisciplined action wastes time. Skills prevent this. |
|
||||
| "I know what that means" | Knowing the concept ≠ using the skill. Invoke it. |
|
||||
| "Let me enter plan mode first" | If a skill handles planning (writing-plans, brainstorming), use the skill directly. EnterPlanMode is redundant — never layer it with a planning skill. |
|
||||
|
||||
## Skill Priority
|
||||
|
||||
|
||||
@@ -5,8 +5,6 @@ description: Use when you have a spec or requirements for a multi-step task, bef
|
||||
|
||||
# Writing Plans
|
||||
|
||||
**IMPORTANT:** Invoke this skill directly — do NOT use EnterPlanMode or platform plan mode. This skill has its own workflow and approval checkpoint (execution handoff). Layering plan mode on top is redundant and restrictive.
|
||||
|
||||
## Overview
|
||||
|
||||
Write comprehensive implementation plans assuming the engineer has zero context for our codebase and questionable taste. Document everything they need to know: which files to touch for each task, code, testing, docs they might need to check, how to test it. Give them the whole plan as bite-sized tasks. DRY. YAGNI. TDD. Frequent commits.
|
||||
|
||||
Reference in New Issue
Block a user