task-decomposer
Task Decomposer
Overview
Break the approved spec and architecture into a small, reviewable task plan for disciplined implementation.
If the work targets a released contract or a new deployed contract version, include compatibility, cutover, and off-chain follow-up tasks instead of treating the change as code-only implementation.
Start Here
Use ../../assets/task-plan-template.md as the output shape.
Write the result to docs/plans/YYYY-MM-DD-<topic>-tasks.md.
Workflow
- Confirm both the spec and architecture artifacts exist.
- Split work into dependency-ordered tasks with clear handoff points.
- Attach explicit verification steps and review checkpoints to each task.
- Make gtest expectations and artifact updates part of the task order.
- If the work changes a released contract surface, add explicit tasks for compatibility review, generated-client updates, and frontend/indexer cutover where relevant.
- Record rollback notes for risky or stateful changes.
Guardrails
- Keep tasks small enough for TDD and frequent commits.
- Do not merge planning, coding, and validation into one step.
- Make prereqs explicit instead of relying on tribal knowledge.
- Keep the plan executable from the artifact chain alone.
- Do not hide release and compatibility work inside a generic “update contract” task.
More from gear-foundation/vara-skills
vara-skills
Use when a builder needs the top-level router for the provisional standard Gear/Vara Sails skill pack across Codex, Claude, or OpenClaw. Do not use for Vara.eth or ethexe work, non-Sails programs, or broad protocol research.
197sails-new-app
Use when a builder is starting a new standard Gear/Vara Sails app and needs the correct greenfield sequence before implementation. Do not use for edits to an established repo, Vara.eth or ethexe targets, or non-Sails templates.
2sails-dev-env
Use when a builder needs to prepare or repair a local macOS, Linux, or Windows machine for standard Gear/Vara Sails Rust development before building, testing, or running a local node. Do not use for live-network deployment, app-specific feature work, or Vara.eth/ethexe-only setup.
2vara-wallet
Use when an agent needs to interact with Vara Network on-chain — deploy programs, call Sails methods, manage wallets, transfer tokens, monitor events. Not for building Sails programs (use vara-skills for that).
2sails-gtest
Use when a builder needs the standard Gear/Vara Sails gtest loop for feature verification, debugging, or regression coverage. Do not use for live-network-only validation, deployment-first workflows, or non-Sails programs.
2sails-frontend
Use when a builder needs to build or extend a React or TypeScript frontend for a standard Gear/Vara Sails app, using Sails-JS, generated clients, React hooks, and low-level Gear-JS only where it adds value. Do not use for Rust-only contract work, raw gstd service design, or non-Vara frontends.
2