Run any Skill in Manus with one click

task-decomposer

Stars17

Forks24

UpdatedMarch 24, 2026 at 12:03

Use when approved spec and architecture artifacts must become an ordered implementation plan for Gear or Vara work. Do not use when the architecture is still unsettled or when the request is only asking for a high-level idea.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

gear-foundation

gear-foundation/vara-skills

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

4 files

SKILL.md

readonly

name	task-decomposer
description	Use when approved spec and architecture artifacts must become an ordered implementation plan for Gear or Vara work. Do not use when the architecture is still unsettled or when the request is only asking for a high-level idea.

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 this repository

same repository

vara-skills

gear-foundation/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. Covers standard Sails apps and ethexe-specific work via dedicated skills. Do not use for non-Sails programs or broad protocol research.

2026-07-1317

vara-wallet

gear-foundation/vara-skills

Use when an agent needs to interact with Vara Network or Vara.eth on-chain — deploy programs, call Sails methods, manage wallets, transfer tokens, monitor events. Do not use for building Sails programs.

2026-07-1317

gear-architecture-planner

gear-foundation/vara-skills

Use when an approved Gear or Vara spec must be mapped onto program boundaries, services, message flow, and integration surfaces. Do not use when the feature is still undefined or when the task is already reduced to code edits.

2026-05-2217

gear-builtin-actors

gear-foundation/vara-skills

Use when a builder needs to design or debug calls from a standard Gear/Vara Sails program into runtime builtin actors such as BLS12-381, staking, proxy, or ETH bridge, including ActorId derivation, request encoding, reply decoding, and gas or ED budgeting. Do not use for regular program-to-program messaging, Vara.eth or ethexe-only work, non-Sails repositories, or runtime-maintenance tasks inside the Gear repo.

2026-05-2217

gear-gstd-api-map

gear-foundation/vara-skills

Use when a builder needs to choose the right gstd API for messaging, execution, reservations, async reply flows, or program creation, and trace that API to gcore or gsys when behavior must be confirmed. Do not use for Vara.eth or ethexe-first work, non-Gear repositories, or broad runtime-maintenance tasks.

2026-05-2217

gear-message-execution

gear-foundation/vara-skills

Use when a builder needs to design or debug Gear message flow, replies, delayed execution, reservations, or waitlist behavior inside a standard Gear/Vara Sails app. Do not use for Vara.eth or ethexe-first work, non-Sails repositories, or broad protocol research.

2026-05-2217

name	task-decomposer
description	Use when approved spec and architecture artifacts must become an ordered implementation plan for Gear or Vara work. Do not use when the architecture is still unsettled or when the request is only asking for a high-level idea.

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.