aidlc-refined-mockups
Run the AI-DLC `refined-mockups` stage (inception phase) in isolation, without advancing the main workflow. Packages `/aidlc --stage refined-mockups --single`: the engine emits one run-stage directive
SKILL.md.claude/skills/aidlc-refined-mockups/SKILL.md
GitHubAI-DLC Stage Runner — refined-mockups
Run the refined-mockups stage on its own. This is opt-in packaging over
/aidlc --stage refined-mockups --single; the same stage is always reachable via
that flag without this skill.
Steps
Ask the engine for the single-stage directive:
aidlc engine orchestrate next --stage refined-mockups --singleThe engine emits one
run-stagedirective forrefined-mockups(carrying the lead agent, the resolved consumes/produces paths, the rules and sensors in context, and the conductor persona on the workflow's first run-stage). When the stage's rules do not fit beside it (most stages on GitHub Copilot, and any stage whose memory files have grown large),load-steeringparts come first instead. For each part, applydirective.rules_contentin array order and keep it as this stage's rules, and adoptconductor_personawhen the part carries it. Then runaidlc engine orchestrate continue <directive.receipt>(the receipt is the 8-character string printed at the top of the directive; copy it, never rebuild it) and act on the directive that comes back. Do not callreportfor a part or tell the user about it. Repeat until therun-stagearrives, show itsstage_validityandchange_noticesonce, and run the stage exactly as it describes; do not load the conductor persona by hand, the engine delivers it.Before acting on the directive, read
.claude/aidlc-common/protocols/stage-protocol.md. Then read every.claude/aidlc-common/protocols/stage-protocol-<module>.mdnamed bydirective.protocol_modules. Load every listed module before reading the stage body or running its topology; skip only a module already loaded earlier in this session.When the stage's work is done, commit the single-stage record:
aidlc engine orchestrate report --single --stage refined-mockups --result completedThis records a STAGE_STARTED / STAGE_COMPLETED pair under a synthetic workflow id and stops. It NEVER writes the main workflow's
Current Stage— a single-stage run is isolated by design (the tool refuses to advance the main workflow).