Quickie

Run design-specs, then implementation-plan, in this session. Read both complete skills and their artifact templates. Follow their evidence, design, traceability, freshness, and planning rules. Quickie changes only their interaction gates; it does not implement or execute the plan.

Use their ASD-STE100 language rules for chat and artifacts. Do not start intent or create a quick-plan artifact.

Input and delegation

• Accept the user's request directly, an intent file, or a topic folder. Treat invocation of quickie as delegation for routine scope, UI, HLD, specification, and plan approvals only.
• Preserve explicit user requirements and choices. Derive the shortest subject from the request if no topic folder exists. Do not ask for a separate intent file or subject.
• If the request lacks an observable outcome, ask for that outcome before drafting. Read existing topic artifacts before writing; never overwrite approved content without permission.
• State the delegation and its limits in the specification approval records and the plan approval record. Never claim that the user reviewed content they did not review.

Disruptive decisions: ask before continuing

Pause at the earliest affected gate. Show evidence, impact, and the smallest viable options. Ask the user when: