Install any skill in seconds. Free to start, no credit card required.
Get Started Free →avizmarlon/docs-as-code
Documentation accompanies code — no code is done without docs. Enforces a minimum documentation checklist per session, maintains a canonical documentation ledger across projects, and synchronizes documentation rules across all tools and agents.
Passed 20 of 22 test cases with the skill, and 13 of 22 without it.
and 7 more in the full report
7 fixed14 passed either way2 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
Our team is beginning work on a new user authentication export feature named `user-export`. Developers usually put design notes in `specs/drafts/user-export.txt`. What is the required location and file naming convention for this new feature specification prior to implementation?
| Checked | Without skill | With skill |
|---|---|---|
| Specifies the feature specification file path as `docs/user-export-spec.md`. | Missed | Passed |
| Mandates creating the specification document prior to code implementation. | Passed | Passed |
The instructions your model reads when the skill loads.
Code without documentation is not done. Documentation is context; context is long-term memory for AI agents and future developers. Without it, each new session or developer starts from zero.
For every session involving code changes, this checklist must be satisfied:
docs/<feature>-spec.md or dedicated section in existing spec)docs/architecture.md updated with structural changes and impactsCHANGELOG.md or equivalent with entry for this changeAll AI agents and developers working on a project must maintain rule parity across tool configurations:
.rules/ or documentation directories must be mirrored in all active development tools (editor configs, linter configs, etc.)CLAUDE.md, AGENTS.md, etc. when they exist) must stay synchronizedDebt visibility principle: If code changes must skip documentation "for now," explicitly record this as doc-debt in a visible location (session-handoff.md, PROGRESS.md, or backlog). Invisible debt is unacceptable; visible debt can be tracked and cleared later.
Every non-trivial software project must maintain these living artifacts in the repository. This applies universally to all projects and teams:
| Artifact | Purpose | Format |
|---|---|---|
| Spec / Charter / README | What the project is, scope, non-goals, decided constraints | Markdown; updated as scope changes |
| ARCHITECTURE.md | System structure, component interfaces, security invariants, extension points | Markdown; keep synchronized with code structure |
| CHANGELOG.md | Versioned record of all changes, using Keep a Changelog format | One entry per significant change, newest at top |
| ADRs (Architecture Decision Records) | Immutable records of architectural and technology decisions | Numbered files in docs/adr/ (e.g., ADR-001-title.md) or single file ARCHITECTURE-DECISIONS.md; format: Title, Number, Date, Status, Context, Decision, Consequences |
| SESSION-HANDOFF.md | State transfer between sessions for multi-session or multi-phase projects | Markdown; preserve unresolved entries; never delete without justification |
test cases passed, vs 13 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.