メニュー
ICM workspace: Resolve documented gaps through intake, prioritization, resolution design, remediation, implementation, and validation. Supports single/batch/systematic scopes.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Orchestrator entry point. Start or resume a multi-component orchestration session. Dispatches one worker per component through the delivery pipeline with wave-based coordination, review gates, execution-discipline enforcement, and inter-wave summary reports. Idempotent — safe to call repeatedly.
Use when implementing any feature or bugfix, before writing implementation code
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
ICM workspace: Coordinate MariloAllocationScheduler spec accuracy, Example UX completeness, visual parity, and source+tests alignment. Stages: spec-review, example-ux, visual-parity, sync-check.
ICM workspace: Gap analysis for MariloAllocationScheduler. Intake, prioritize, design, plan, implement, validate. Stages: 01-intake through 06-validate.
ICM workspace: Plan, sequence, and execute implementation passes for the Marilo PM Demo. Covers settings pages, asset management, dynamic forms, inspections, deficiencies, and domain expansion. 6 stages.
| name | gap-analysis-resolution |
| description | ICM workspace: Resolve documented gaps through intake, prioritization, resolution design, remediation, implementation, and validation. Supports single/batch/systematic scopes. |
| argument-hint | [setup|status|ingest|resolve|close] |
| allowed-tools | Read Glob Grep Edit Write |
You are entering an Interpretable Context Methodology (ICM) workspace. The folder structure IS the orchestration — numbered folders are stages, markdown files carry prompts and context.
ICM/workspaces/gap-analysis-resolution/CLAUDE.md — this is the workspace routing layer$ARGUMENTS is provided, treat it as a trigger keyword and follow the Triggers table in CLAUDE.mdICM/workspaces/gap-analysis-resolution/CONTEXT.md for task routing_status/workspace-status.md first (Layer 0 snapshot — not authoritative)_config/coverage-summary.md for batch-level detail_config/gap-context.md for full configuration and resolution trackingsingle skips 02+04 | batch skips 04 | systematic runs all 6output/ folder. The next stage reads from there.| Keyword | Action |
|---|---|
setup | Run onboarding questionnaire |
status | Show pipeline completion for all stages |
ingest | Fast path: paste/point to gap analysis file, jump to Stage 01 import mode |
resolve | Start or continue resolution design (Stage 03) |
close | Jump to validation (Stage 06) for a specific gap |