Name: ito-proposal
Author: withakay

Prompt file imported from withakay/renzu (.codex/prompts/ito-proposal.md). Fill in {{arguments}} before use. Copyright stays with the author.

The user has requested the following change proposal. {{arguments}}

Use the Ito agent skill ito-write-change-proposal (alias: ito-proposal) as the source of truth for this workflow.

Input

The request is provided in the prompt arguments or block. Use it to scope the change and name the change ID.

Module selection

Prefer a semantic fit in an existing module: run ito list --modules and choose the closest match by purpose/scope.
If no module is a good fit, propose creating a new module for the theme of the work.

Instructions

Tell the model to use the ito-write-change-proposal skill to complete this workflow, using any supplied arguments or context from the prompt.

Audit guardrail (GitHub Copilot)

In GitHub Copilot repository-agent sessions, treat audit checks as mandatory before stateful Ito actions: run ito audit validate first.
If validation fails or drift is reported, run ito audit reconcile and use ito audit reconcile --fix when remediation is required.

Testing Policy (TDD + coverage)

Follow the Testing Policy printed by ito agent instruction proposal / ito agent instruction apply.
Default workflow: RED/GREEN/REFACTOR (write a failing test, implement the minimum to pass, then refactor).
Coverage target: 80% (guidance; projects may override).
Override defaults via cascading project config (low -> high precedence): ito.json, .ito.json, .ito/config.json, $PROJECT_DIR/config.json (when set).
Keys: defaults.testing.tdd.workflow, defaults.testing.coverage.target_percent.

{
  "defaults": {
    "testing": {
      "tdd": { "workflow": "red-green-refactor" },
      "coverage": { "target_percent": 80 }
    }
  }
}

Guardrails

If the ito-write-change-proposal skill is missing or unavailable, ask the user to run ito init (or ito update if the project is already initialized), then stop.
Do not duplicate the full workflow here; defer to the skill guidance.

Install ito-proposal and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

The user has requested the following change proposal. <UserRequest> {{arguments}} </UserRequest>  Use the Ito agent skill `ito-write-change-proposal` (alias: `ito-proposal`) as the source of truth for this workflow. **Input** - The request is provided in the prompt arguments or <UserRequest> block. Use it to scope the change and name the change ID. **Module selection** - Prefer a semantic fit in an existing module: run `ito list --modules` and choose the closest match by purpose/scope. - If no module is a good fit, propose creating a new module for the theme of the work. **Instructions** Tell the model to use the `ito-write-change-proposal` skill to complete this workflow, using any supplied arguments or context from the prompt. **Audit guardrail (GitHub Copilot)** - In GitHub Copilot repository-agent sessions, treat audit checks as mandatory before stateful Ito actions: run `ito audit validate` first. - If validation fails or drift is reported, run `ito audit reconcile` and use `ito audit reconcile --fix` when remediation is required. **Testing Policy (TDD + coverage)** - Follow the Testing Policy printed by `ito agent instruction proposal` / `ito agent instruction apply`. - Default workflow: RED/GREEN/REFACTOR (write a failing test, implement the minimum to pass, then refactor). - Coverage target: 80% (guidance; projects may override). - Override defaults via cascading project config (low -> high precedence): `ito.json`, `.ito.json`, `.ito/config.json`, `$PROJECT_DIR/config.json` (when set). - Keys: `defaults.testing.tdd.workflow`, `defaults.testing.coverage.target_percent`. ```json { "defaults": { "testing": { "tdd": { "workflow": "red-green-refactor" }, "coverage": { "target_percent": 80 } } } } ``` **Guardrails** - If the `ito-write-change-proposal` skill is missing or unavailable, ask the user to run `ito init` (or `ito update` if the project is already initialized), then stop. - Do not duplicate the full workflow here; defer to the skill guidance.

{ "prompt": "The user has requested the following change proposal.\n<UserRequest>\n{{arguments}}\n</UserRequest>\n\n\n\nUse the Ito agent skill `ito-write-change-proposal` (alias: `ito-proposal`) as the source of truth for this workflow.\n\n**Input**\n\n- The request is provided in the prompt arguments or <UserRequest> block. Use it to scope the change and name the change ID.\n\n**Module selection**\n\n- Prefer a semantic fit in an existing module: run `ito list --modules` and choose the closest match by purpose/scope.\n- If no module is a good fit, propose creating a new module for the theme of the work.\n\n**Instructions**\n\nTell the model to use the `ito-write-change-proposal` skill to complete this workflow, using any supplied arguments or context from the prompt.\n\n**Audit guardrail (GitHub Copilot)**\n\n- In GitHub Copilot repository-agent sessions, treat audit checks as mandatory before stateful Ito actions: run `ito audit validate` first.\n- If validation fails or drift is reported, run `ito audit reconcile` and use `ito audit reconcile --fix` when remediation is required.\n\n**Testing Policy (TDD + coverage)**\n\n- Follow the Testing Policy printed by `ito agent instruction proposal` / `ito agent instruction apply`.\n- Default workflow: RED/GREEN/REFACTOR (write a failing test, implement the minimum to pass, then refactor).\n- Coverage target: 80% (guidance; projects may override).\n- Override defaults via cascading project config (low -> high precedence): `ito.json`, `.ito.json`, `.ito/config.json`, `$PROJECT_DIR/config.json` (when set).\n- Keys: `defaults.testing.tdd.workflow`, `defaults.testing.coverage.target_percent`.\n\n```json\n{\n \"defaults\": {\n \"testing\": {\n \"tdd\": { \"workflow\": \"red-green-refactor\" },\n \"coverage\": { \"target_percent\": 80 }\n }\n }\n}\n```\n\n**Guardrails**\n\n- If the `ito-write-change-proposal` skill is missing or unavailable, ask the user to run `ito init` (or `ito update` if the project is already initialized), then stop.\n- Do not duplicate the full workflow here; defer to the skill guidance.\n\n", "variables": [ "arguments" ], "notes": "Scaffold a new Ito change and validate strictly.", "metadata": { "source": { "provider": "github-codex-prompts", "repository": "https://github.com/withakay/renzu", "path": ".codex/prompts/ito-proposal.md", "ref": "ca4bcd3e65e05f8aad129fab428953804531ef0d", "url": "https://github.com/withakay/renzu/blob/ca4bcd3e65e05f8aad129fab428953804531ef0d/.codex/prompts/ito-proposal.md", "key": "withakay/renzu/.codex/prompts/ito-proposal.md" } } }

ito-proposal

About

Install ito-proposal and it becomes one more candidate the router can pick - when it fits.

Use it

Manifest

Reviews