feO2x/guided-coding / claude-plugin/claude-skills/write-plan
write-plan
UnverifiedWrite a Guided Coding plan or follow-up plan after its approach has been discussed. Run only when explicitly requested by the user or by another Guided Coding skill.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 2.5 KB |
| assets/default-plan-structure.md | markdown | 1.5 KB |
| assets/rdat-plan-structure.md | markdown | 5.0 KB |
assets/default-plan-structure.md
View on GitHub# Default Guided Coding Plan Structure
Start with `# Title`, followed by exactly these sections in order:
1. `## Rationale`: briefly state the problem and the goal of this issue.
2. `## Acceptance Criteria`: list **observable, verifiable outcomes** as unchecked Markdown tasks (`- [ ]`). Describe results, not implementation steps.
3. `## Technical Details`: record the technical guidance the implementer needs, such as APIs to extend, design patterns to follow, testing and benchmark guidance, links to relevant documentation, and any performance, threading, or security constraints. Include only what is relevant. Avoid step-by-step instructions and exhaustive listings. Assume the implementer is a senior software developer.
Use minimal code examples only when they clarify an important contract, such as an API signature, interface, or DTO shape. Say whether an example is exact or illustrative. Avoid method bodies, step-by-step instructions, exhaustive file lists, and routine background.
When behavior changes, require automated test coverage in the acceptance criteria. Require benchmarks only when performance is a material risk or requirement.
The root `AGENTS.md` and its referenced documents should list the repository's feedback loops, such as compilers, static analyzers, automated tests, code coverage, mutation testing, and benchmarks. Use them to make acceptance criteria verifiable. If there are no feedback loops listed, stop and report this to the user.
If the plan requires a missing feedback loop, make adding it explicit in the plan.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 467k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |