issue-spec

Create GitHub issues as lean-spec style specifications for human-AI aligned implementation on whatever repo this skill is installed in. GitHub issues are the sole spec medium — no spec files.

This skill is the repo-agnostic methodology half of the contract. Each consumer repo overlays its own delta in two places:

• Repo CLAUDE.md — names the GitHub slug (codervisor/lean-spec, onsager-ai/onsager, onsager-ai/duhem, …) and any repo-specific spec principles (e.g. Onsager's Reach + seam rule, lean-spec's provider-agnostic core + i18n, Duhem's worked-example + schema-impact).
• <repo>-dev-process sister skill — carries the area-label taxonomy, the spec-vs-trivial gate, the SDD loop wiring, and the repo's pre-push check gate + CI-failure patterns.
• Global pre-push / pr-lifecycle skills — the shared pre-push and post-push methodology (installed from onsager-ai/dev-skills). The consumer repo overlays only its gate command, collision patterns, and any pr-spec-sync automation via CLAUDE.md / <repo>-dev-process; the skills themselves are not per-repo.

When in doubt about the target repo, run git remote -v and read the repo's CLAUDE.md and its *-dev-process skill before drafting the spec body.

Why GitHub Issues, Not Files

lean-spec uses Markdown files with YAML frontmatter for metadata. We replace that entirely with GitHub issues because: