superpowers plan

AI Community

Skill notes

When to use this skill

any multi-file change any change that impacts behavior, data, auth, billing, or production workflows any debugging that needs systematic isolation

Planning rules

Steps should be small (2–10 minutes each). Every step must include verification. Prefer incremental deliverables (avoid “big bang” edits). Identify rollback and risk controls early.

Plan

Step name Files: path/to/file.ext, ... Change: (1–2 bullets) Verify: (exact commands or checks) ...

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
AI
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@anthonylee991 · no license declared
Token usage
Lean
Setup complexity
Plug-and-play
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Author source file SKILL.md

# Planning Skill

## When to use this skill
- any multi-file change
- any change that impacts behavior, data, auth, billing, or production workflows
- any debugging that needs systematic isolation

## Planning rules
- Steps should be **small** (2–10 minutes each).
- Every step must include **verification**.
- Prefer **incremental deliverables** (avoid “big bang” edits).
- Identify **rollback** and **risk controls** early.

## Plan format (use this exact structure)
### Goal
### Assumptions
### Plan
1. Step name
   - Files: `path/to/file.ext`, `...`
   - Change: (1–2 bullets)
   - Verify: (exact commands or checks)
2. ...

### Risks & mitigations
### Rollback plan

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.