egm-draft

Topics in the source

• Design Drafting (Document Construction)
• Execution Constraints (CRITICAL)
• Inputs
• Execution Workflow
• Section Approval Gate (Steps 2–5)
• Step 1: Ingest Predecessor Context (Concepts Brief or Notes)
• Step 2: Draft Overview, Goals & Problem Statement
• Step 3: Draft Technical Plan

When running in Codex or ChatGPT Work, first read Codex integration. In Claude Code or Cowork, read ${CLAUDEPLUGINROOT}/docs/claude.md first. This skill guides the user through drafting a technical design document based on the aligned problem and requirements from the brainstorm phase. 1. You MUST read and apply the execution instructions in resources/executioninstructions.md. 2. Artifact-First Delivery (MANDATORY): You are STRICTLY FORBIDDEN from presenting large proposals, drafts, summaries, or plans directly in the chat pane. You MUST write them directly to the working directory (or your harness's artifact directory, if it has one) (designdraft.md or ./designdraft.md) using your file-writing tool and tell the user in chat the file path and ask for review. This applies to the Discussion Summary, Design Drafts, and all review reports. 3. Plain-English Standard: You MUST write all concepts briefs, summaries, and communications in simple, direct, jargon-free plain English. Explain technical mechanisms directly. Do not summarize away substance or rely on buzzwords. Do not use ungrounded promotional adjectives (e.g., seamless, robust, blazingly fast) or decorative adverbs (e.g., seaml

This is an excerpt. Refer to the complete source and its current requirements.