target-spec-bootstraplisted

Create the target repository's local spec skeleton and reusable requirements/design/tasks templates. Use from repo-init-scan during first substantial plugin use, or from spec-writing flows when `spec/INDEX.md` or `spec/templates` is missing. Do not overwrite active project specs.
funky-eyes/best-copilot · ★ 10 · AI & Automation · score 79

Install: claude install-skill funky-eyes/best-copilot

# Target Spec Bootstrap Use this skill to create the target repository's spec routing structure. Specs are target-local delivery artifacts; this skill carries the installable templates. ## Boundary - Write into the target repository, never into the installed plugin package or plugin cache. - Create missing files only. Do not overwrite active specs or project-specific templates. - Do not copy this plugin repository's active specs, memory, or workflow examples into the target repository. Generate only neutral target-local templates. - Use specs for MEDIUM/LARGE requirements, design, tasks, acceptance checks, and ADRs. - Link active specs to `memories/repo/current-workstreams.md` when persistent recovery is needed. ## Files Create these paths when absent: - `spec/INDEX.md` - `spec/templates/requirements-template.md` - `spec/templates/design-template.md` - `spec/templates/tasks-template.md` ## `spec/INDEX.md` ```markdown # Spec Index  | Directory | Tags | Last updated | Status | Linked memory | Summary | | --- | --- | --- | --- | --- | --- | | `spec/templates/` | template, requirements, design, tasks | unknown | template | `memories/repo/workflow-rules.md` | Reusable templates for new spec bundles | ## Maintenance Rules - Every MEDIUM/LARGE feature gets a spec directory with `requirements.md`, `design.md`, and `tasks.md`. - Add a row here when creating a spec. - Link active specs back to `memories/repo/current-workstreams.md`. - Mark