DocSlime
Make repo knowledge stick. DocSlime absorbs product intent, requirements, design,
architecture, tests, and decisions into one local docs body that humans and agents can use.
repo/
|-- docs/
| |-- PRODUCT.md
| |-- DESIGN.md
| |-- 2-REQUIREMENTS.md
| |-- 3-ARCHITECTURE.md
| |-- 4-TESTING.md
| `-- 3-ENGINEERING/ADRs/
`-- .agents/skills/
|-- docslime-fill
|-- docslime-adr
`-- docslime-kiss
DocSlime is a small CLI plus a skill pack for creating, filling, reviewing, and publishing an
opinionated docs/ tree. The name is silly on purpose; the method is not. It pulls the
scattered parts of a project into one integrated body, then gives future humans and AI agents
better context for the next change.
Why It Sticks
product intent -> PRODUCT.md + DESIGN.md
behavior -> REQUIREMENTS.md + TESTING.md
system shape -> ARCHITECTURE.md + ADRs
maintenance -> docslime-fill + docslime-adr + docslime-kiss
publication -> docmd.io
- Product and design context flows into
PRODUCT.mdandDESIGN.md, so agents stop
guessing what the code is for. - Requirements and behavior flow into
2-REQUIREMENTS.mdand4-TESTING.md, so TDD+BDD
work can trace back to intent. - Domain shape and tradeoffs flow into
3-ARCHITECTURE.mdand3-ENGINEERING/ADRs/, so
Domain Driven Design language stays close to decisions. - Human judgment flows through
docslime-fill,docslime-adr, anddocslime-kiss, so
docs get filled, decisions get recorded, and bloat gets cut.
Install DocSlime
Homebrew is the recommended local install path:
brew install DecisionNerd/tap/docslime
docslime init creates missing docs and reports what was created or skipped. It will not
overwrite existing files unless --force is explicit. The slime eats context, not your
worktree.
Other install paths stay available when Homebrew is not the right fit.
curl -LsSf \
https://github.com/DecisionNerd/DocSlime/releases/latest/download/docslime-installer.sh \
| sh
cargo install \
--git https://github.com/DecisionNerd/DocSlime \
--bins
First Run Path
docslime init
Create the standard docs tree and leave clear next steps in the repo.
npx skills add DecisionNerd/DocSlime
Use docslime-fill to interview the team and replace scaffold guidance with real context.
docslime add adr choose-storage-boundary
Record significant product and technical choices while they are still fresh.
Run docslime-kiss as an agent skill to find bloat, contradictions, stale placeholders, and
weak traceability before docs become ceremony.
What DocSlime Creates
docs/
|-- PRODUCT.md
|-- 1-EXPERIENCES.md
|-- 2-REQUIREMENTS.md
|-- DESIGN.md
|-- 3-ARCHITECTURE.md
|-- 4-TESTING.md
|-- 0-PRODUCT/
|-- 1-JOURNEYS/
`-- 3-ENGINEERING/ADRs/
docs/PRODUCT.md and docs/DESIGN.md are deliberately discoverable from the docs tree so
tools like impeccable can load product and design context without duplicate root files.
- Product + design:
PRODUCT.md,DESIGN.md, and0-PRODUCT/capture purpose,
voice, principles, and success measures. - Experiences + requirements:
1-EXPERIENCES.md,1-JOURNEYS/, and
2-REQUIREMENTS.mdmap human and agent journeys to testable behavior. - Architecture + ADRs:
3-ARCHITECTURE.mdand3-ENGINEERING/ADRs/keep domain
boundaries and decisions explicit. - Testing:
4-TESTING.mdties TDD and BDD coverage back to requirements and journeys.
Agent Skills
DocSlime keeps judgment-heavy work in skills instead of pretending every review belongs in a
CLI subcommand.
docslime-installanddocslime-initverify the CLI and scaffold the docs tree without
overwriting existing work.docslime-fillinterviews the user, replaces scaffold guidance, and keeps facts anchored
in the repo.docslime-adrcreates the next-numbered ADR and writes the decision in the project
vocabulary.docslime-kissreviews for contradictions, generic AI prose, weak traceability, and
overgrown docs.