First week pack
Use this after you copy [`scaffold/`](scaffold/) into your repository. Goal: a **usable** docs spine in about one working week for a small team — not every folder filled.
First week pack
Use this after you copy scaffold/ into your repository. Goal: a usable docs spine in about one working week for a small team — not every folder filled.
Day 0 — Copy the kit (≤ 30 minutes)
- Copy into your repo root (adjust if monorepo):
scaffold/docs/→docs/(includesGOVERNANCE.md+KIT.md)scaffold/.github/workflows/docs.ymlscaffold/.github/PULL_REQUEST_TEMPLATE.md(merge if you already have one)scaffold/AGENTS.mdscaffold/.markdownlint.json- Optionally
scaffold/llms.txt.example→llms.txt
- In the product repo, open
docs/KIT.mdand setKIT_URLto this primer repo (clone path or GitHub URL). - Read
docs/GOVERNANCE.md(stub policy) and this file (you can keep a bookmark toFIRST_WEEK.mdupstream). - Canonical map while working from the kit:
appendix/phase-folder-map.md. In the product repo, use the path names listed indocs/KIT.mdunless you vendor the map.
Minimum files to make real (the “7+” pack)
Fill or replace these first. Everything else can stay as folder READMEs until the phase arrives.
| # | Create / fill | Template or example |
|---|---|---|
| 1 | docs/internal/charter/vision.md |
templates/vision-charter.md · Acme vision |
| 2 | docs/internal/charter/scope.md |
same template (Scope section) |
| 3 | docs/shared/glossary.md |
start from scaffold glossary · Acme glossary |
| 4 | One user story under docs/internal/requirements/ |
templates/user-story.md · Acme story |
| 5 | At least three NFR rows in docs/internal/requirements/non-functional.md |
templates/nfr.md · Acme NFRs |
| 6 | One ADR in docs/internal/decisions/ |
templates/adr.md · Acme ADR-001 |
| 7 | docs/user/getting-started/quickstart.md |
Acme quickstart |
| 8 | (If you expose an API) one module spec + OpenAPI stub | Acme export-service · OpenAPI sample |
Optional the same week if you already page on-call:
| + | File | Example |
|---|---|---|
| 9 | One symptom runbook under docs/internal/operations/runbooks/ |
Acme queue backlog |
What you may ignore in week 1
Per scaffold/docs/GOVERNANCE.md:
- Empty phase folders beyond the files above
coverage-reports/,performance-benchmarks/, changelog history, retirement docs- Publishing to MkDocs/Docusaurus/Mintlify — enable
scaffold/.github/workflows/docs.ymllint/link first; site recipes come later
Definition of done for week 1
-
docs/KIT.mdhas a realKIT_URL(or an explicit local path note) - Charter vision + scope committed
- Glossary has product-specific terms (not only kit defaults)
- At least one testable user story + numeric NFRs
- At least one ADR for a real decision (or a “proposed” ADR for an open decision)
- User quickstart exists (even if “coming soon” sections are marked TODO)
- Docs CI workflow runs on PRs that touch
docs/ - PR template docs checklist is in use
- No broken
../primer/...(or similar) links inside copieddocs/files
Next
- Walk phases in
LEARNING_PATH.mdas you build - Compare patterns in
examples/acme-export-platform/ - When OpenAPI exists, turn on Spectral in the workflow (see commented job in
docs.yml)