Write Plan
Turn an approved spec into dependency-aware tasks with file scopes, acceptance mapping, and verification. Skip obvious small changes.
Install
$ agentstack add skill-bnet47-codexicon-write-plan ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README — it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-bnet47-codexicon-write-plan) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming — see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps — measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Write an implementation plan
Announce: "I'm using write-plan to turn the approved spec into verifiable implementation tasks."
Inputs
Read the selected approved spec, relevant architecture and conventions, applicable ADRs, and the current target code. Do not assume the newest spec is the right one when several are present; identify it from the request or links.
Task design
- Map every acceptance criterion to at least one task and verification step.
- Order tasks by real dependency. Identify tasks that are safe to run in parallel.
- Keep tightly coupled edits in one task. Do not split work to satisfy a time or file-count quota.
- Give each task the smallest coherent file scope and name existing interfaces precisely.
- Include migrations, compatibility behavior, error paths, and tests when required by the spec.
- Do not include commits, pushes, deployments, or external writes unless the approved scope explicitly authorizes them.
Output
Save agent_docs/plans/[YYYY-MM-DD]-[feature-slug]-plan.md:
# Implementation Plan: [Feature]
**Spec:** [relative link]
**Date:** [YYYY-MM-DD]
## Global constraints
- [Constraint all tasks must preserve.]
## Acceptance mapping
| Criterion | Task(s) | Evidence |
|---|---|---|
| AC-1 | 1, 3 | [test or inspection] |
### Task 1: [Coherent outcome]
**Depends on:** none | Task N
**Parallel-safe with:** [task numbers or none]
**Files:** create/modify/test exact paths
**Behavior:** [complete expected behavior and error handling]
**Interfaces:** [signatures, schemas, events, or commands]
**Verification:** `[exact command]`
**Done when:** [observable completion condition]Self-review for spec coverage, stale paths, undefined interfaces, unsafe parallelism, placeholders, and runnable verification. Offer $execute-plan when delegation is useful; otherwise the primary agent can implement the plan directly.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: bnet47
- Source: bnet47/codexicon
- License: MIT
- Homepage: https://bnet47.github.io/codexicon/repo-template-playbook.html
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.