- Home
- Skills
- Technical Documentation
- make docs
make docs
Automated architecture and behavioral documentation for codebases using BCP 14 standards.
$5
Works with the AI Agents you already use
make docs
Example session with this skill installed
I just finished the new authentication module. Can you run /make-docs update to sync the documentation?
- Read your context and instructions
- Compiled the make docs
I have surveyed the recent changes in the src/auth directory and identified new logic for JWT validation and session persistence. I have updated the documentation suite to reflect these observable behaviors.
Documentation Update: Auth Domain
The following files were updated to match the current implementation:
Updated Files
docs/README.md(Timestamp refreshed)docs/specs/auth.md(Added session persistence requirements)docs/architecture/domains/api.md(Updated auth endpoints)
# Auth Spec
## Session Validation
The system SHALL invalidate sessions immediately upon a `POST /logout` request.
### Scenario: User Logout
**Given** an active session token `JWT_A`
**When** the user sends a `POST /auth/logout` with `JWT_A`
**Then** subsequent requests with `JWT_A` SHALL return a `401 Unauthorized` status.
## Token Expiry
The system SHALL issue tokens with a maximum lifespan of 3600 seconds as defined in `config/auth.yaml`.
Next steps
- Review the new
SHALLrequirements indocs/specs/auth.mdto ensure they match the intended business logic. - Verify that the updated API endpoints in
docs/architecture/domains/api.mdcorrectly reflect the new controller signatures. - Commit the changes to the
docs/directory to maintain the sync stamp.
Connects securely to your tools. The creator never sees your data.
About this skill
Maintaining accurate documentation for a shifting codebase is a manual chore that often leads to outdated specs and architecture drift. This skill automates the discovery, creation, and maintenance of project documentation by surveying the source code and enforcing BCP 14 standards.
The skills is free on my Github, the $5 amount is a way to show your appreciation for the work behind this project.
What it does
- Source-code surveying analyzes your tree to identify architecture patterns and behavioral domains.
- Automated spec generation produces documentation focusing on observable outcomes using BCP 14 keywords.
- Architecture mapping creates structured guides for domains, APIs, constraints, and glossaries based on evidence.
- Decision tracking records Architecture Decision Records (ADR) and updates the architecture map if boundaries change.
- Delta synchronization compares current code against the documentation stamp to update only what changed.
How it works
- Run
/make-docs exploreto trigger the survey phase where the agent identifies evidence and confirms the brief. - The agent generates the documentation suite using specific templates for READMEs, specs, and architecture files.
- Use
/make-docs updateor/make-docs refreshto sync docs with recent code changes or regenerate the entire suite. - Call
/make-docs adrto document specific design decisions and their associated costs or benefits.
Frameworks & tools
This skill is framework-agnostic and works with any codebase. It relies on a structured docs/ layout and follows BCP 14 (RFC 2119/8174) for requirement language.
Why this beats prompting it yourself
Generic prompts often produce "fluff" or hallucinations about how code works. This skill enforces an evidence-based approach where every claim must cite a specific path, config, or command, ensuring the docs reflect reality rather than intent.
Use cases
- Generating a new architecture suite for a legacy repository.
- Keeping behavioral specs in sync with rapid PR merges.
- Formalizing architecture decisions (ADRs) during a migration.
- Auditing a codebase to identify unearned or missing documentation.
Known limitations
Does not document data models, observability, or CI/CD pipelines. Requires a specific references/ directory containing phase files and templates to function.
Does not cover data models, observability, or CI/CD.
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 any payment.
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 1 month ago