IT

ito-write-change-proposal

Manages the lifecycle of feature changes from proposal to implementation tasks.

Install

mkdir -p .claude/skills/ito-write-change-proposal && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/14655" && unzip -o skill.zip -d .claude/skills/ito-write-change-proposal && rm skill.zip

Installs to .claude/skills/ito-write-change-proposal

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Use when creating, designing, planning, proposing, or specifying a feature, change, requirement, enhancement, fix, modification, or spec. Use when writing tasks, proposals, specifications, or requirements for new work.
218 chars✓ has a “when” trigger
Beginner

Key capabilities

  • Create a new change with a specified module
  • Generate proposal artifacts for a change
  • Generate specification artifacts for a change
  • Generate design artifacts for a change
  • Generate task artifacts for a change
  • Follow project-specific testing policies

How it works

The skill creates a new change or uses an existing one, then executes `ito agent instruction` commands to generate various artifacts like proposals, specs, design, and tasks.

Inputs & outputs

You give it
A change ID or a request to create a new change with a name and module
You get back
Generated proposal, specs, design, and task artifacts

When to use ito-write-change-proposal

  • Proposing new features
  • Generating project specs
  • Creating implementation tasks

About this skill

Create or continue a change, then generate proposal/spec/design/tasks using the CLI instruction artifacts.

Testing Policy (TDD + coverage)

  • Default workflow: RED/GREEN/REFACTOR (write a failing test, implement the minimum to pass, then refactor).
  • Coverage target: 80% (guidance; projects may override).
  • Override keys (cascading config): defaults.testing.tdd.workflow, defaults.testing.coverage.target_percent
  • When available, follow the "Testing Policy" section emitted by ito agent instruction proposal|apply; it reflects project configuration.

Steps

  1. If the user provided an existing change ID, use it. Otherwise, create a new change:

    • Pick a module (default to 000 if unsure).
    • Run:
      ito create change "<change-name>" --module <module-id>
      
  2. Generate the artifacts (source of truth):

    ito agent instruction proposal --change "<change-id>"
    ito agent instruction specs --change "<change-id>"
    ito agent instruction design --change "<change-id>"
    ito agent instruction tasks --change "<change-id>"
    
  3. Follow the printed instructions for each artifact exactly.

When not to use it

  • When the user does not need to create or modify a change proposal
  • When the user is not working with `ito` commands

Limitations

  • The skill relies on the `ito` command-line interface.
  • The skill's output is limited to the artifacts generated by the `ito agent instruction` commands.

How it compares

This skill automates the generation of multiple change proposal artifacts using CLI commands, unlike manually creating each document.

Compared to similar skills

ito-write-change-proposal side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
ito-write-change-proposal (this skill)05moReviewBeginner
create-plan368moReviewBeginner
project-planner3210moReviewIntermediate
system-design199moNo flagsIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

You might also like

create-plan

antinomyhq

Generate detailed implementation plans for complex tasks. Creates comprehensive strategic plans in Markdown format with objectives, step-by-step implementation tasks using checkbox format, verification criteria, risk assessments, and alternative approaches. Use when users need thorough analysis and structured planning before implementation, when breaking down complex features into actionable steps, or when they explicitly ask for a plan, roadmap, or strategy. Strictly planning-focused with no code modifications.

36121

project-planner

adrianpuiu

Comprehensive project planning and documentation generator for software projects. Creates structured requirements documents, system design documents, and task breakdown plans with implementation tracking. Use when starting a new project, defining specifications, creating technical designs, or breaking down complex systems into implementable tasks. Supports user story format, acceptance criteria, component design, API specifications, and hierarchical task decomposition with requirement traceability.

32115

system-design

lagz0ne

Use when designing, architecting, or planning a new system from requirements or ideas - transforms concepts into navigable design catalog using EventStorming methodology, Mermaid diagrams, and progressive elaboration through 5 phases (Requirements, Big Picture, Processes, Data/Flows, Integration)

19108

spec-kit-workflow

jmanhype

Guides specification-driven development workflow. Automatically invoked when discussing new features, specifications, technical planning, or implementation tasks. Ensures proper workflow phases (specify → clarify → plan → checklist → tasks → analyze → implement).

11111

sparc-methodology

ruvnet

SPARC (Specification, Pseudocode, Architecture, Refinement, Completion) comprehensive development methodology with multi-agent orchestration

8100

spec-workflow

TencentCloudBase

Standard software engineering workflow for requirement analysis, technical design, and task planning. Use this skill when developing new features, complex architecture designs, multi-module integrations, or projects involving database/UI design.

1091

Search skills

Search the agent skills registry