Use ASD-STE100 Simplified Technical English when you ask questions or write output files.
Turn an initial development prompt into a shared, user-validated understanding. Clarification establishes what the request means. It does not decide how to implement it.
Invariants
- Do not write formal requirements, solution design, implementation tasks, or production code.
- Do not turn every request into a project. If the user only wants an explanation or impact assessment, use
explore. - Never run
git commit, create branches, or push changes.
Artifact lifecycle
The output is a context brief based on assets/context-brief-template.md.
- Use
docs/agentic-engineering/context/<YYYY-MM-DD>/<subject>.md. - If a matching draft exists, offer to resume it before creating another file.
- After the initial evidence pass, save the brief with
status: draftandcheckpoint: framing. - Update the brief after each material answer so an interrupted session can resume from the unresolved questions.
- Before presenting it for approval, set
checkpoint: awaiting-validation. - Apply requested changes until the user approves it. Then set
status: validatedandcheckpoint: complete. - On write failure, report the failure and stop. Never claim that unsaved context is resumable.
Workflow
- Read
references/facilitation-rules.mdbefore asking questions. - Inspect relevant repository files, documentation, tests, public behavior, and recent commits. If no repository exists or the request is greenfield, state the evidence limitation.
- Read any exploration artifact supplied by the user. Treat it as evidence, not as a decision or a commitment to build.
- Draft the initial request, problem, current behavior, desired outcome, known scope, constraints, assumptions, and unresolved questions. Save the draft.
- Ask one focused question at a time. Ask only questions whose answers materially change the brief or unblock requirements.
- Keep the brief current during the conversation. Distinguish user statements, repository evidence, inference, and unknowns.
- Present the Confirmed Understanding section as a concise restatement. Ask the user to validate it.
- On approval, validate the artifact and report its path as optional input to
requirements.
Boundaries
- Capture a proposed solution as intent or an assumption. Do not evaluate alternatives unless the user switches to
explore. - Capture success signals in ordinary language. Do not create
FR-*,NFR-*, orAC-*identifiers. - Do not ask design questions about APIs, schemas, libraries, or internal architecture unless the answer is already a user constraint.
- Do not ask questions already answered by repository evidence or a supplied exploration.
- Do not require complete certainty. Record non-blocking unknowns and let requirements own later precision.
Completion check
The brief is ready for validation only when it states:
- The initial request and why it matters.
- Current behavior with evidence, or a greenfield statement.
- The desired outcome and affected users.
- In-scope and out-of-scope boundaries.
- Known constraints, assumptions, and unresolved questions.
- A concise Confirmed Understanding that the user can approve or correct.