# Ito Proposal

> 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.

- Skill: `tomevault-io/ito-proposal` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add tomevault-io/ito-proposal`
- Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/ito-proposal/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: tomevault-io (https://skillmd.com/u/tomevault-io)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/tomevault-io/ito-proposal

---


Collaborate with the user to understand their intent, then create a change and generate proposal artifacts.

**If the user already provided a change ID**, skip to Step 4 (Generate artifacts) — the change already exists.

**Step 0: Understand the change (do this first)**

Do NOT jump straight into creating files. Interview the user to build a shared understanding:

- Ask clarifying questions one at a time. Prefer multiple-choice when possible.
- Identify: What problem does this solve? Why now? What does success look like?
- Surface ambiguity early — if something is unclear or could be interpreted multiple ways, ask.
- Explore scope: What's in? What's explicitly out? Are there simpler alternatives?
- If the user's request is vague, propose 2-3 interpretations and ask which fits.
- If the request is already well-defined, confirm your understanding and move on — don't over-interview.

Only proceed to Step 1 once you and the user agree on what the change is and why it matters.

**Step 1: Choose a schema**

```bash
ito agent instruction schemas
```

If the user has no preference, recommend **spec-driven** (default).

**Step 2: Confirm the module (mandatory gate)**

⛔ **Do NOT create any change scaffolding until the user has confirmed their module choice.**

1. Run `ito list --modules` to show available modules and sub-modules.
2. Present the user with these options and **wait for their response**:
   - **Use an existing module** — pick from the list (provide the ID)
   - **Create a new module** — enter a name (`ito create module "<name>"`)
   - **Create a new sub-module** under an existing module — specify parent ID and name (`ito create sub-module "<name>" --module <parent-id>`)
3. Do NOT silently default to module `000`. Always ask.

**Step 3: Create the change**

After the user confirms the module:

```bash
# For a module:
ito create change "<change-name>" --module <module-id> --schema <schema>

# For a sub-module:
ito create change "<change-name>" --sub-module <NNN.SS> --schema <schema>
```

**Step 4: Generate artifacts**

```bash
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>"
```

Follow the printed instructions for each artifact exactly.

**Testing Policy**

- Default workflow: RED/GREEN/REFACTOR. Coverage target: 80% (projects may override).
- Follow the "Testing Policy" section emitted by `ito agent instruction proposal|apply`.

---
> Converted and distributed by [TomeVault](https://tomevault.io/claim/withakay) — claim your Tome and manage your conversions.
<!-- tomevault:4.0:skill_md:2026-04-13 -->