Writing plans
Skill roronoazoroshao369/vibe-coding-os/skills/core/writing-plans
Vibe Coding OS — Claude/Codex/Cursor skill framework with 139 skills, 111 commands, 95 templates, 22 tracked sources, 28/28 validation gates PASS. Quality Shield, Engineering Discipline Pack, plugin marketplace.From the repository description
npx -y skills add roronoazoroshao369/vibe-coding-os --skill writing-plansAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
2.3 KB, 454 tokens by cl100k_base, as published. Nobody here has run it
Skill: Writing Plans
Purpose
Turn an approved spec or clear request into an executable, reviewable plan with file targets, risks, and checks.
When to use
Use after brainstorming/spec approval and before multi-step implementation, refactors, migrations, reference integrations, or risky bug fixes.
Inputs
Approved spec or requirement summary, repo conventions, target files, constraints, validation commands, and known risks.
Workflow
- Confirm the spec or requirement is authoritative; if not, pause for approval or record the assumption.
- Inspect likely files and registries before proposing edits.
- Break the work into small tasks with owners or file scopes when parallel work is useful.
- Attach a verification step to each meaningful behavior or structure change.
- Call out dependencies, rollback points, and tasks that must not happen.
- Keep the plan concise enough to execute and update it when discoveries change the path.
Outputs
A concrete implementation plan with scope, file targets, ordered tasks, risks, rollback points, and validation commands.
Failure modes
- Plan ignores existing repo conventions.
- Plan is so broad that review becomes impossible.
- Verification is postponed or vague.
- The plan is treated as approval for requirements the user did not accept.
Verification checklist
- Scope and non-scope are clear.
- Each step is actionable and ordered.
- Risky files or decisions are named.
- Validation commands are explicit.
Choose instead
Turning a chosen direction into a step-by-step implementation plan with checkpoints.
If this skill is not the right phase for your task, use one of these instead:
skills/core/brainstorming/SKILL.md— if the direction is not yet chosen.skills/core/spec-first-development/SKILL.md— if no spec exists and one is needed before planning.skills/core/plan-driven-execution/SKILL.md— if the plan is already written and you want to execute it.
For the full decision tree across all 6 plan-family skills, see docs/workflows/plan-skill-decision-tree.md.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.