What problem does it solve? Changes to a test framework's core infrastructure — KATA base classes, fixture APIs, the CLI installer, or the OpenAPI type-sync pipeline — carry high regression risk because every test depends on them. This Skill enforces a planning gate and structured pipeline so architectural changes are reviewed, verified, and archived instead of being improvised. ## Core Features & Use Cases - Gated four-phase pipeline: Plan → Code → Verify → Archive with subagent dispatch, session resume checks, and a mandatory preflight toolchain gate. - Path guardrails: ALLOWED/FORBIDDEN path tables in references/kata-invariants.md prevent framework work from leaking into per-ticket test specs owned by other skills. - Parallel verification: runs test suite, typecheck, lint, and skill-registry checks concurrently before accepting any change. - Use Case: When adding a new fixture API to the Playwright-based KATA framework, the skill plans the change against kata-manifest.json, implements it in batches, verifies with four parallel checks, and archives the session artifacts. ## Quick Start Ask the AI to evolve the framework by describing the infrastructure change, for example: run /framework-development to add a new fixture API to the KATA test framework.
