- Home
- Skills
- Technical Documentation
- Git Wiki Spec Builder: Commit-Pinned Product Specs
Git Wiki Spec Builder: Commit-Pinned Product Specs
- **Wiki only**: reads `hot.md` → `Index.md` → Domains → Topics → Concepts and recent build logs.
$1
Works with the AI Agents you already use
Git Wiki Spec Builder: Commit-Pinned Product Specs
Example session with this skill installed
Write the spec from the current wiki so I can hand it to the coding agent.
- Read your context and instructions
- Compiled the git wiki spec
$ python3 scripts/spec_preflight.py
mode : git branch=main N=7 H=07add28
wiki pages : 6 in WIKI/
spec target : SPEC/SPEC_commit_7.md
frontmatter : title, base_commit: 07add28, base_number: 7, created: 2026-10-26
WARNING : Source/ changed since the last wiki build:
Source/research/pricing-ideas.md
STALE : the wiki does not reflect the latest Source/ — recommend running wiki-build first
→ User chose to continue; pricing is marked Undecided.
SPEC/SPEC_commit_7.md (excerpt)
### F1 Real-time collaborative editing (WIKI/Topic/realtime-collaborative-editing.md)
- State: each note = Yjs CRDT doc; offline edits in IndexedDB.
- Transport: WebSocket primary; SSE + HTTP POST fallback when the upgrade fails.
- Acceptance:
- AC1 Two editors see each other's changes within 1 s on a normal connection.
- AC2 Edits made offline are merged without loss after reconnect.
- AC3 With WebSocket blocked, editing still syncs via the SSE+POST fallback.
### F2 Action items (WIKI/Topic/action-items-tracking.md)
- Input: a note line `- [ ] @owner task text due:YYYY-MM-DD`
- Output: {id, note_id, owner, text, due_date, status: open|done, created_at}
- AC2 "My items" lists only the signed-in user's open items, by due date.
## Unresolved / open questions
1. Offline search: server-side PostgreSQL vs offline requirement — Undecided
2. Does completing an item in "My items" tick the note checkbox? — Undecided
3. Authentication / team membership model — Undecided (not in wiki)
4. Pricing — Undecided (in Source, not yet in wiki)
$ python3 scripts/verify_spec.py SPEC/SPEC_commit_7.md
Spec check passed — 1 file(s)
Ready to commit: git add SPEC && git commit -m "spec: SPEC_commit_7 (base 07add28)"
Summary: 3 features · 8 "Undecided" markers · 0 open contradictions
Connects securely to your tools. The creator never sees your data.
About this skill
The problem
Specs written from memory or raw notes drift from what the team actually consolidated, and coding agents happily build on invented details.
What it does
- Preflight: finds the project, checks the optional branch guard, and warns STALE when Source changed after the last wiki build. It continues only if you say so.
- Wiki only: reads
hot.md→Index.md→ Domains → Topics → Concepts and recent build logs.Source/is never used as evidence. - Writes
SPEC/SPEC_commit_<N>.mdwithbase_commit/base_numberfrontmatter. It switches to a split folder with anoverview.mdindex when large. - Sections: overview · problem · users & scenarios · one feature spec per Topic with acceptance criteria · tech stack & why · data & structure · risks · open questions.
- No invention: gaps are marked Undecided.
conflict/in-reviewpages are quoted as open questions with their status, never as fact. Key decisions cite wiki pages. - verify_spec.py checks frontmatter, ASCII names, split-folder index and links. Then it commits (asks first unless
auto_commit). Works with Git Wiki Builder (builds the wiki) and Git Wiki Ask (cited Q&A).
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Technical Documentation.
Only as complete as the wiki; it deliberately refuses to fill gaps. Staleness is judged from committed Source changes; uncommitted edits aren't detected. verify_spec checks structure, not content quality. It doesn't implement the spec; hand it to your coding agent.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 22 days ago
- Software
Python 3
Git
Permissions
File Scopes
Reads Source/ paths only for the staleness check; no network; never pushes; local commit only with approval.