Framework Core — Foundation references + bootstrap

framework-core is the skill that other skills assume already exists. It plays two distinct roles in the same package:

1. Passive — shared reference library. Workflow skills (sprint-testing, test-documentation, test-automation, regression-testing, project-discovery) cite files under references/ instead of duplicating the same briefing template, dispatch patterns and orchestration doctrine inside every skill. Loading a workflow skill therefore implies loading the relevant framework-core/references/*.md on demand.
2. Active — bootstrap trigger. When users adopt this boilerplate by downloading skills à la carte (e.g. cloning .claude/skills/sprint-testing/ only), they end up missing the foundation files those skills depend on (AGENTS.md, .agents/project.yaml, scripts/agents-*.ts, etc.). Invoking /framework-core init regenerates that foundation from the templates shipped under templates/.

Without framework-core, every other workflow skill would either silently rely on files that don't exist or copy-paste the same boilerplate-foundation paragraphs into its own references/. This skill is the single source of truth for both.

Two roles

Passive role: nobody invokes framework-core directly to read a reference — they just cite framework-core/references/<file>.md and the AI loads it. Active role: only the user invokes it, and only when foundation files are missing.