メニュー
ICM workspace: Coordinate MariloAllocationScheduler spec accuracy, Example UX completeness, visual parity, and source+tests alignment. Stages: spec-review, example-ux, visual-parity, sync-check.
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: 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.
ICM workspace: Migrate ASP Classic (VBScript/.asp) pages to .NET Core Blazor. Stages: inventory-assessment, architecture-design, data-layer-migration, page-conversion, integration-validation.
| name | allocation-scheduler-delivery |
| description | ICM workspace: Coordinate MariloAllocationScheduler spec accuracy, Example UX completeness, visual parity, and source+tests alignment. Stages: spec-review, example-ux, visual-parity, sync-check. |
| argument-hint | [setup|status|spec|demo|visual|sync|deliver] |
| allowed-tools | Read Glob Grep |
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/allocation-scheduler-delivery/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/allocation-scheduler-delivery/CONTEXT.md for task routingoutput/ folder. The next stage reads from there.stages/*/output/ — files present (excluding .gitkeep) = COMPLETE, otherwise PENDING| Keyword | Action |
|---|---|
setup | Run onboarding questionnaire |
status | Show pipeline completion for all stages |
spec | Enter stages/01-spec-review/CONTEXT.md |
demo | Enter stages/02-example-ux/CONTEXT.md |
visual | Enter stages/03-visual-parity/CONTEXT.md |
sync | Enter stages/04-sync-check/CONTEXT.md |
deliver | Run all four stages in sequence |
src/Marilo.Components/DataDisplay/AllocationScheduler/MariloAllocationScheduler.razor.csdocs/component-specs/allocation-scheduler/tests/Marilo.Tests.Unit/DataDisplay/AllocationScheduler/ICM/workspaces/allocation-scheduler-gap-analysis/ — source changes and test writing are delegated there.