ForgeMySpec

Safely amends an existing ForgeMySpec spec.yaml in response to new information discovered during implementation (wrong assumption, tightened constraint, scope change). Proposes only the minimal delta, validates the result with lint, and shows a diff before writing. Never rewrites the whole spec without explicit user approval.

Compiles a human requirement into a validated operational spec (spec.yaml) and Claude execution artifacts (CLAUDE.md, acceptance checklist, implement command, scope eval seeds). Use when the user wants spec-driven development, a concrete execution contract before coding, or to reduce scope drift. Prefer this skill inside Claude Code where MCP tools can supply repository, docs, or ticket context before drafting the spec.

Implements work strictly from an existing ForgeMySpec bundle (spec.yaml, CLAUDE.md, acceptance checklist). Use when the spec is already written and the user wants coding execution without re-compiling the requirement. Combines well with MCP tools for reading tests, CI, and repo structure during implementation.