woc-feature-plan
/woc-feature-plan
Plan a large or multi-session World of ClaudeCraft feature as architecture-aligned vertical slices with explicit decisions, verification, and handoff state. Use when the user requests a phased implementation plan, planning packet, session breakdown, or scalable approach before implementation.
- Author
- rowdybard ↗
- Repository
- whetstorm-art ↗
- Licence
- MIT
- Last repository change
- 25.10.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 25.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Plan a large or multi-session World of ClaudeCraft feature as architecture-aligned vertical slices with explicit decisions, verification, and handoff state. Use when the user requests a phased implementation plan, planning packet, session breakdown, or scalable approach before implementation.
Original author description
Plan a large or multi-session World of ClaudeCraft feature as architecture-aligned vertical slices with explicit decisions, verification, and handoff state. Use when the user requests a phased implementation plan, planning packet, session breakdown, or scalable approach before implementation.
How it works
- Research before planning
- Define the change
- Build vertical phases
- Persist only useful state
SKILL.md preview
--- name: woc-feature-plan description: "Plan a large or multi-session World of ClaudeCraft feature as architecture-aligned vertical slices with explicit decisions, verification, and handoff state. Use when the user requests a phased implementation plan, planning packet, session breakdown, or scalable approach before implementation." --- # Feature Plan Create the smallest planning artifact that makes a large feature safe to execute across sessions. ## Research before planning 1. Read the root and relevant local `CLAUDE.md` files. 2. Run `git status --short` and preserve unrelated work. 3. Inspect production paths, tests, module seams, and relevant project documentation. 4. Use bounded parallel exploration for independent subsystems. 5. Fetch current official documentation for version-sensitive external interfaces. 6. When work adds or changes SQL, a database call site, stored-data growth, scheduled database work, pool sizing or admission, transaction or lock scope, or timeout policy; a database driver/dependency version, or PostgreSQL engine/resource/configuration/topology, use `woc_database_performance` for a read-only scaling pass. When work adds a `selfWireJson` key or changes the `src/sim/` read one calls, a recurring server job, an event-driven durability write, or a `world_state` blob, use `woc_server_hot_path` for the non-SQL budget (the grown-collection rules in `server/CLAUDE.md` "Hot paths"). Do not create planning files until the goal, scope, and important constraints are understood. Ask the user when a choice would materially change architecture or product behavior. ## Define the change Record current behavior and ownership, desired behavior and acceptance criteria, affected systems and platforms, constraining invariants, decisions already made, truly blocking open decisions, and compatibility, migration, localization, privacy, security, database performance, and testing implications. For database-backed work, record expected query frequency and cardinality, the index/cache/pagination strategy, pool and lock impact, version-sensitive timeout/planner assumptions, and the measured evidence the implementation must produce. Reference canonical instructions instead of copying them. ## Build vertical phases Prefer phases that deliver a testable behavior slice. Each phase states: 1. Outcome and explicit scope. 2. Expected modules or seams. 3. Tests to add or update. 4. Validation commands and manual verification. 5. Exit criteria. 6. State needed by the next phase. Keep a phase small enough for one focused session when practical. Do not isolate documentation that belongs beside its implementation. ## Persist only useful state If the user requests planning files, use a minimal packet: - `implementation-plan.md` for architecture, decisions, phases, and completion criteria. - `progress.md` for verified phase status. - `state.md` for the exact resume point, blocker, and next action. Add per-phase files only when a phase needs substantial independent detail. Starter prompts must be model-neutral and include the goal, relevant files, canonical constraints, authorized actions, checks, and handoff. Do not pin a model or effort. Planning does not authorize implementation, commits, pushes, issues, or pull requests. Do not modify `CLAUDE.md` or `.claude/**` as Codex support work. Return the phases, unresolved decisions, risk areas, and recommended first executable step.
Files in this package (2)
- SKILL.md 3 KB
- agents/openai.yaml 1 KB
Versions
The database has no other skills named woc-feature-plan.
Database snapshot: 13.11.2026 · package version 890b818a2ffe (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100woc-qa
Run end-of-contribution QA for World of ClaudeCraft, including readiness checks, scoped regression testing, and conditional specialist review. Use when asked to QA changes, make work ready, verify a branch or worktree, or assess whether a contribution is complete. - 95Plan
Generate implementation plans from feature specifications with foundation-aware template selection, dependency analysis, and phased execution strategy. USE WHEN plan, implementation plan, how to implement, execution plan, technical approach, planning, create plan. - 90woc-review-pr
Review a World of ClaudeCraft pull request against its actual diff, canonical architecture, tests, and domain risks. Use when asked to inspect, review, assess, or prepare feedback for a pull request. Reading and drafting are allowed by default, but posting GitHub feedback… - 90planning
Creates and reviews executable implementation plans grounded in repository evidence, with vertical slices, explicit decisions, and verification criteria. Use when asked to "plan this feature", "stress-test this plan", "grill me", or "split this into tickets". For architecture… - 100plan-feature
Structured feature planning workflow. Use when the user says "plan a feature", "design this", "how should we build", "feasibility check", or any pre-implementation planning work. Covers requirements, investigation, feasibility, and implementation planning. - 100plan-feature
Use when the user says "plan a feature", "design this", "how should we build", or before writing code for any non-trivial feature. Produces an approved task breakdown before implementation begins — plan first, build second.