context-authoring

# context-authoring ## When to use Use this skill when: - A new project has been scaffolded and the `agents/settings/contexts/` files are still template stubs from `event4u/agent-config`. - The user asks "help me fill in the auth model context", "set up tenant boundaries", or similar knowledge-layer work. - A reviewer skill (`authz-review`, `data-flow-mapper`, `migration-safety`, `multi-tenant-boundary-review`, `secrets-and-config-review`) reports *"I cannot proceed — `agents/settings/contexts/<file>.md` is still a template"*. - After a significant architecture change that invalidates one of the five context files. Do NOT use when: - Writing a regular roadmap or feature doc — use `agent-docs-writing`. - Creating a generic context document that does not map to one of the five knowledge-layer templates — use `context-create`. - Filling in the engineering-memory YAML files (`domain-invariants.yml`, etc.) — use `/memory-add`. ## The five files | File | What it answers | Who reads it | |---|---|---| | `auth-model.md` | Roles, permission model, impersonation, known exceptions | `authz-review`, `judge-security-auditor`, `threat-modeling` | | `tenant-boundaries.md` | Tenancy type, scope propagation, known cross-tenant paths | `multi-tenant-boundary-review`, `blast-radius-analyzer`, `judge-security-auditor` | | `data-sensitivity.md` | Field classification, masking rules, log-safe types | `data-flow-mapper`, logging reviewers | | `deployment-order.md` | Migration s...