drafterlisted

# Drafter Skill Generate governance documents using Charter's project context, ADF modules, and current repository state. ## Use When Use this skill when the user asks to draft, write, formalize, or generate governance documentation such as: - ADRs - Policy documents - Decision records - Operating agreements - Compliance documents If the request is ambiguous, ask: "What governance document would you like to draft?" ## Instructions ### 1. Detect Project Context Identify the project and its governing context before drafting. Preferred sources: 1. Charter MCP tools, if available: - `getProjectContext` for the relevant task or topic - `getArchitecturalDecisions` for load-bearing constraints - `getProjectState` for current validation state and active issues - `getRecentChanges` for recent work that may affect the document 2. Local Charter artifacts, if MCP is not available: - `.ai/manifest.adf` - `.ai/core.adf` - `.ai/state.adf` - Relevant on-demand modules such as `decisions.adf`, `planning.adf`, `backend.adf`, `frontend.adf`, or `content.adf` 3. Repository context: - `package.json`, `wrangler.toml`, or current directory name for project identity - Existing governance docs in directories like `docs/`, `adrs/`, `ADR/`, `decisions/`, `policies/`, or `compliance/` - Recent issues, PRs, changelog entries, or design notes when available Never invent project constraints that are not supported by the available Charter or repository context.