Immutable. This exact content is served forever at /api/v1/blob/3f3ee0e23ae81529.
--- name: project-context description: "Generate or refresh the canonical business context maps and master test plan. Use for business-data-map, business-feature-map, business-api-map, master-test-plan, refresh project context, refresh all context, entity map, feature inventory, API business map, or risk-ranked test roadmap. Routes exactly one mode at a time unless refresh-all is explicit. UPDATE mode always shows a diff and waits for approval before overwriting." license: MIT compatibility: [claude-code, copilot, cursor, codex, opencode] complementary_categories: [testing-e2e, testing-api, meta-skill] --- # Project Context Own the four regenerative project-context artifacts without duplicating their workflows across harness commands. ## Mode routing Resolve one mode from the invocation. Load only the reference named in that row. | Mode | Legacy alias / trigger | Reference | Output | |---|---|---|---| | `data` | `business-data-map`, entity/data map | `references/data.md` | `.context/business/business-data-map.md` | | `features` | `business-feature-map`, feature inventory | `references/features.md` | `.context/business/business-feature-map.md` | | `api` | `business-api-map`, API business map | `references/api.md` | `.context/business/business-api-map.md` | | `test-plan` | `master-test-plan`, risk-ranked test roadmap | `references/test-plan.md` | `.context/master-test-plan.md` | | `refresh-all` | refresh all project context | all four references, one at a time | all four outputs | If the user does not identify a mode, ask which artifact to refresh. Do not infer `refresh-all` from a generic request. ## `refresh-all` dependency order Run sequentially and complete each reference's own validation and approval gate before loading the next: 1. `data` 2. `features` 3. `api` 4. `test-plan` Stop on a hard dependency failure or rejected overwrite. Do not skip ahead. Missing soft dependencies remain Discovery Gaps exactly as each reference defines. ## Shared contract - Read every available source required by the selected reference. Never invent business facts. - CREATE mode may write the missing artifact after analysis. - UPDATE mode must generate a candidate, show the diff summary, and wait for explicit approval before overwriting. - Each output includes `## Discovery Gaps` for unverified facts. - After a successful artifact write, update the canonical instruction/context pointers in `AGENTS.md` only when a pointer is missing. Never add operational prose to `CLAUDE.md`. - `$ARGUMENTS` are forwarded unchanged to the selected mode.