artgraph-bootstrap

Solid

Bootstraps spec ↔ code ↔ test traceability tags in an existing project by proposing spec entries and `[REQ-NNN]` markers on covering test titles as a reviewable diff (code-side `@impl REQ-NNN` tags only where no test exists), then verifying deterministically with `artgraph scan && artgraph check` and, when tests ran with the artgraph/vitest runner, `artgraph trace report`. Use when the user asks to bootstrap / cold-start / seed traceability / add initial REQs to an untagged or partially-tagged project. Make sure to use this skill whenever the user mentions bootstrap / cold-start / initial REQ seeding for artgraph.

Code & Development 10 stars 1 forks Updated today MIT

Install

View on GitHub

Quality Score: 78/100

Stars 20%
35
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

## Purpose Cold-starts traceability on a project that has few or no REQ tags today. Where a covering test already exists for a candidate requirement, the agent (probabilistically) proposes ONLY the test-side closure — a `- REQ-NNN:` spec entry plus a `[REQ-NNN]` marker on the covering test title — and does NOT touch implementation code; once the user approves and the tests run, the coverage-derived `exercises` edge corroborates (or contradicts) the tag mechanically, no LLM needed. Only in areas with no test to tag at all does the agent fall back to the older code-side proposal (spec entry + `// @impl REQ-NNN`), and the proposal must say so explicitly. This split — LLM proposes, artgraph verifies deterministically — is the **determinism boundary**: link generation may be probabilistic, but link verification must be reproducible without an LLM in the loop. The Skill never writes trace tags without first showing a diff and getting explicit user approval. ## Preconditions Committed clean working tree recommended: uncommitted changes cannot be cleanly rolled back with `git reset` if the user approves apply. ## Steps Every Bash tool call is a **fresh shell** — variables do not persist across calls; carry the detected PM and any per-step counts forward as plain text in your reasoning, not shell variables. `<PM-exec>` is the project's package runner — `npx artgraph`, `pnpm exec artgraph`, `bunx artgraph`, or `deno run -A npm:artgraph/cli` — substitute the one detected by `_share...

Details

Author
mori-shin-x
Repository
mori-shin-x/artgraph
Created
1 months ago
Last Updated
today
Language
TypeScript
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category