메뉴
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.
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: Migrate ASP Classic (VBScript/.asp) pages to .NET Core Blazor. Stages: inventory-assessment, architecture-design, data-layer-migration, page-conversion, integration-validation.
| name | pm-demo-builder |
| description | 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. |
| argument-hint | [setup|status] |
| allowed-tools | Read Glob Grep Edit Write |
You are entering an Interpretive Context Methodology (ICM) workspace. The folder structure IS the orchestration — numbered folders are stages, markdown files carry prompts and context.
ICM/workspaces/pm-demo-builder/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/pm-demo-builder/CONTEXT.md for task routingoutput/ folder. The next stage reads from there.samples/Marilo.PmDemo/SETTINGS_STATUS.md — always read this, not copies| Keyword | Action |
|---|---|
setup | Run onboarding — asks about which build pass to execute (settings, assets, dynamic forms, etc.) |
status | Show pipeline completion for all six stages |
shared/implementation-guardrails.md — agreed architecture and coding rulesshared/component-inventory.md — existing Marilo components available to the demoshared/shell-and-ia.md — app shell, navigation, layout conventions_config/pm-demo-context.md — current state assessment from samples/Marilo.PmDemo_config/domain-expansion.md — asset management, dynamic forms, inspections scopesamples/Marilo.PmDemo (Blazor Server via Aspire, EF Core + PostgreSQL, DAB + GraphQL, Wolverine messaging)IUserNotificationService already implemented and wired