Summary
Define the first real git-mind semantic bootstrap slice for an unfamiliar repository.
This issue exists because the backlog currently has supporting work for packaging, docs, contracts, and hardening, but almost no issue that names the core product move directly: point Git Mind at a repo and get a useful first semantic map with low manual input.
Sponsor User
A technical lead, staff engineer, architect, or autonomous coding agent dropped into an unfamiliar repository who needs a trustworthy mental model quickly.
Job To Be Done
When I point git-mind at a repository, help me understand how its code, docs, ADRs, commits, and adjacent artifacts relate without making me manually author the graph first.
Desired Playback Evidence
We should be able to run Git Mind on a representative unfamiliar repo and demonstrate:
- a useful first-pass semantic map appears before the user feels like they are doing data entry
- at least a small set of inferred relationships are visible with provenance and confidence
- the result is obviously incomplete, but already useful for repo understanding
Scope
Define and agree on:
- the first artifact set to ingest
- the first entity types to extract
- the first relationship types to infer
- the provenance model for inferred assertions
- the confidence model for first-pass suggestions
- the first commands or flows that expose the bootstrap result
- the top 5 questions this slice should help answer on day one
Suggested Starting Artifact Set
- repository file tree and module/package structure
- markdown docs
- ADRs
- commit history
- issue / PR references discoverable from repo-local artifacts
Exit Criteria
- a concrete first-slice spec exists and is accepted
- follow-on implementation issues can be created from that spec
- the issue backlog visibly reflects Hill 1 rather than only supporting work
Summary
Define the first real
git-mindsemantic bootstrap slice for an unfamiliar repository.This issue exists because the backlog currently has supporting work for packaging, docs, contracts, and hardening, but almost no issue that names the core product move directly: point Git Mind at a repo and get a useful first semantic map with low manual input.
Sponsor User
A technical lead, staff engineer, architect, or autonomous coding agent dropped into an unfamiliar repository who needs a trustworthy mental model quickly.
Job To Be Done
When I point
git-mindat a repository, help me understand how its code, docs, ADRs, commits, and adjacent artifacts relate without making me manually author the graph first.Desired Playback Evidence
We should be able to run Git Mind on a representative unfamiliar repo and demonstrate:
Scope
Define and agree on:
Suggested Starting Artifact Set
Exit Criteria