Turn your repo into living docs.

brew install DecisionNerd/tap/docslime

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

strategy -> product/design -> discovery -> requirements -> architecture -> testing
    ^                                                               |
    +----------- observation <- publishing <- verified build <------+

• Product and design context flows into PRODUCT.md and DESIGN.md, so agents stop
  guessing what the code is for.
• Continuous discovery lives in experience/, where evidence and journeys become
  solution-neutral requirements rather than an untraceable feature backlog.
• Requirements and behavior flow into REQUIREMENTS.md and engineering/TESTING.md, so
  TDD+BDD work can trace back to evidence.
• Domain shape and tradeoffs flow into engineering/ARCHITECTURE.md and engineering/adrs/, so
  Domain Driven Design language stays close to decisions.
• Human judgment flows through docslime-fill, docslime-adr, and docslime-kiss, so
  docs get filled, decisions get recorded, and bloat gets cut.
• Delivery and observation close the loop: engineering/PUBLISHING.md defines promotion,
  verification, and rollback; engineering/OBSERVABILITY.md connects production health and
  user outcomes back to discovery.

Install DocSlime

Homebrew is the recommended local install path:

brew install DecisionNerd/tap/docslime

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

npx skills add DecisionNerd/DocSlime

docslime add adr choose-storage-boundary

The recommended happy path is short: install the CLI, run docslime init, add the skill
pack, fill docs/PRODUCT.md, then use docslime-kiss once the first useful context exists.

What DocSlime Creates

docs/
|-- README.md
|-- PRODUCT.md
|-- DESIGN.md
|-- REQUIREMENTS.md
|-- strategy/README.md
|-- experience/README.md
`-- engineering/
    |-- README.md
    |-- ARCHITECTURE.md
    |-- TESTING.md
    |-- PUBLISHING.md
    |-- OBSERVABILITY.md
    `-- adrs/README.md

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, and strategy/ capture purpose,
  voice, principles, and success measures.
• Experience + requirements: experience/ captures evidence, opportunities, journeys,
  and hypotheses; REQUIREMENTS.md translates them into a testable build contract.
• Architecture + ADRs: engineering/ARCHITECTURE.md and engineering/adrs/ keep domain
  boundaries and decisions explicit.
• Testing: engineering/TESTING.md ties TDD and BDD coverage back to requirements and journeys.
• Publishing + observability: engineering/PUBLISHING.md and
  engineering/OBSERVABILITY.md carry verified artifacts to
  users and feed production evidence back into discovery.

Agent Skills

DocSlime keeps judgment-heavy work in skills instead of pretending every review belongs in a
CLI subcommand.

• docslime-install and docslime-init verify the CLI and scaffold the docs tree without
  overwriting existing work.
• docslime-fill interviews the user, replaces scaffold guidance, and keeps facts anchored
  in the repo.
• docslime-adr creates the next-numbered ADR and writes the decision in the project
  vocabulary.
• docslime-kiss reviews for contradictions, generic AI prose, weak traceability, and
  overgrown docs.

Read Next