project-documentationComplete workflow for project documentation including ADRs, PRDs, personas, and docs organization. Use when setting up documentation for a new project or improving existing docs. Triggers on project documentation, ADR, PRD, personas, docs structure, documentation setup.
Install via ClawdBot CLI:
clawdbot install wpank/project-documentationComplete workflow for setting up and maintaining project documentation.
npx clawhub@latest install project-documentationStart every project with documentation, not code:
1. Define the idea ā What is this? What problem does it solve?
2. Define the personas ā Who uses this? What are their journeys?
3. Define the features ā What does it do for each persona?
4. Define the stack ā What technologies? Why?
5. Then build ā With full context establisheddocs/
āāā architecture/ # CURRENT STATE - Living docs of actual code
ā āāā overview.md
ā āāā data-flow.md
āāā guides/ # CURRENT STATE - How to use/operate
ā āāā getting-started.md
ā āāā configuration.md
āāā runbooks/ # CURRENT STATE - Short, actionable guides
ā āāā local-dev.md
ā āāā deploy.md
ā āāā database.md
āāā planning/ # FUTURE - Not for docs site
ā āāā roadmap.md
ā āāā specs/
āāā decisions/ # ADRs - Decision records
ā āāā 001-tech-stack.md
ā āāā 002-auth-approach.md
āāā product/ # PRD, personas
āāā overview.md
āāā personas/
āāā features.md| Category | Purpose | Goes on Docs Site? |
|----------|---------|-------------------|
| Current State | How things work now | Yes |
| Planning | Future specs, designs | No |
| Architecture | Living docs of code | Yes |
| Roadmap/Todos | What we're working on | No |
| Runbooks | How to operate | Yes |
| Proposed Runbooks | Future plans | No |
Template:
# ADR-001: [Title]
## Status
[Proposed | Accepted | Deprecated | Superseded]
## Context
[What is the issue we're solving?]
## Decision
[What did we decide?]
## Consequences
[What are the results - positive and negative?]
## Alternatives Considered
[What other options did we evaluate?]Template:
# PRD: [Feature Name]
## Problem
[What problem are we solving?]
## Users
[Which personas does this serve?]
## Requirements
- [ ] Requirement 1
- [ ] Requirement 2
## Non-Goals
[What are we explicitly NOT doing?]
## Success Metrics
[How do we know this worked?]Template:
# Persona: [Name]
## Who They Are
- Background
- Technical level
- Goals
## Pain Points
- [Pain 1]
- [Pain 2]
## Journey
1. Discovery
2. Onboarding
3. Daily use
4. Advanced usage
## Content Needs
- Doc types they need
- Format preferencesTemplate:
# Runbook: [Task Name]
## Prerequisites
- [Requirement 1]
- [Requirement 2]
## Steps
1. [Step 1]
2. [Step 2]
## Verify
[How to confirm success]
## Troubleshooting
| Problem | Solution |
|---------|----------|
| [Issue] | [Fix] |## Roadmap
### Current Sprint
- [ ] Add user authentication endpoint
- [ ] Create login form component
- [ ] Wire form to auth endpoint
### Backlog
- [ ] Password reset flow
- [ ] OAuth integration
- [ ] Two-factor authBefore shipping docs:
Generated Mar 1, 2026
A tech startup needs to establish clear documentation from day one to align the team, attract investors, and onboard early users. This skill helps create PRDs, define user personas, and set up a structured docs directory, ensuring all stakeholders understand the product vision and current state without confusion from future planning.
An enterprise IT team is overhauling outdated systems and requires standardized documentation for architecture decisions, runbooks for operations, and guides for developers. This skill aids in creating ADRs to justify tech stack choices and separate current operational docs from future migration plans, reducing downtime and training costs.
A digital agency handles various client projects simultaneously and needs consistent documentation workflows to maintain quality and efficiency. This skill enables setting up persona docs for client audiences, PRDs for feature requests, and runbooks for deployment, ensuring clear communication and repeatable processes across teams.
An open-source project seeks to grow its contributor base by providing clear documentation for new developers. This skill helps structure guides for getting started, architecture overviews, and decision records, making it easier for volunteers to understand the codebase and contribute effectively without overwhelming them with planning details.
Companies offering software as a service rely on this skill to document user personas and PRDs for feature development, ensuring product alignment with customer needs. It supports recurring revenue by improving user onboarding and retention through clear, actionable runbooks and guides.
Consulting firms use this skill to standardize documentation for client deliverables, such as ADRs for architecture recommendations and persona docs for user research. It enhances service quality and billable hours by providing structured, reusable templates that reduce project setup time.
PLG companies focus on user self-service and adoption through intuitive products. This skill aids in creating docs-first workflows with clear runbooks and guides, driving organic growth by enabling users to easily understand and use the product without extensive support.
š¬ Integration Tip
Integrate this skill early in project lifecycles to establish a docs-first culture; use the provided templates to ensure consistency and avoid mixing current and future documentation, which reduces confusion.
Use the mcporter CLI to list, configure, auth, and call MCP servers/tools directly (HTTP or stdio), including ad-hoc servers, config edits, and CLI/type generation.
Connect to 100+ APIs (Google Workspace, Microsoft 365, GitHub, Notion, Slack, Airtable, HubSpot, etc.) with managed OAuth. Use this skill when users want to...
Build, debug, and deploy websites using HTML, CSS, JavaScript, and modern frameworks following production best practices.
YouTube Data API integration with managed OAuth. Search videos, manage playlists, access channel data, and interact with comments. Use this skill when users want to interact with YouTube. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway).
Scaffold, test, document, and debug REST and GraphQL APIs. Use when the user needs to create API endpoints, write integration tests, generate OpenAPI specs, test with curl, mock APIs, or troubleshoot HTTP issues.
Search for jobs across LinkedIn, Indeed, Glassdoor, ZipRecruiter, Google Jobs, Bayt, Naukri, and BDJobs using the JobSpy MCP server.