القائمة
Start a feature-oriented Ito change proposal with feature-biased intake and schema recommendations.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Implement Ito Lite markdown changes by reading proposal/spec/design/tasks artifacts and updating manual task statuses. Use when applying or executing a prompt-only Ito Lite change without the ito CLI.
Archive completed Ito Lite changes by manually merging spec deltas into current specs and moving the change to archive. Use after implementation and verification when no ito CLI is available.
Create prompt-driven Ito Lite change proposal packages in markdown. Use for drafting proposal.md, spec deltas, optional design.md, and tasks.md without the ito CLI or validation executable.
Review Ito Lite markdown proposal packages before implementation. Use to check proposal.md, spec deltas, design.md, and tasks.md for consistency, risk, testability, and manual validation without the ito CLI.
Initialize a markdown-only Ito Lite workspace with no executables. Use when setting up prompt-driven change proposals, creating .ito-lite/project.md, or preparing a repo for Ito-style specs, changes, and tasks without the ito CLI.
Coordinate the prompt-only Ito Lite workflow for proposals, specs, tasks, reviews, implementation, and archive without the ito executable. Use when the user asks for Ito-style planning, change proposals, lightweight specs, or markdown-only change management.
| name | ito-feature |
| description | Start a feature-oriented Ito change proposal with feature-biased intake and schema recommendations. |
Use this when the user is introducing a new capability, expanding an existing one, or otherwise framing the work as a feature.
If the user already provided a change ID, skip to Step 5 (Continue with ito-proposal) — the change already exists.
Drive proposal creation through a feature-oriented intake lane that gives the user enough discovery without forcing a fix-shaped workflow.
ito-proposal-intake.spec-driven for new capabilities, behavior changes, and ambiguous feature workminimalist only if the requested enhancement is unusually bounded and low-risktdd when the feature is best introduced by writing tests against the desired behavior firstevent-driven if the feature is centered on event or message workflow behaviorito-brainstorming.ito-proposal using the intake summary as the shared understanding.ito-fix or the neutral ito-proposal lane.ito-feature is an opinionated front door, not a separate schema.ito-proposal lane.