persona-docs

What This Skill Does

The persona-docs skill is a specialized agentic tool designed to bootstrap the user-centered documentation lifecycle for software projects. It enables OpenClaw to generate structured, professional persona profiles, user journey maps, and onboarding flows. By analyzing existing codebase metadata and documentation, the skill creates a 'North Star' for development, ensuring that every subsequent feature, UI/UX adjustment, and technical architectural decision is aligned with the needs of the actual end-user. It turns abstract project goals into concrete, actionable user-centric data points.

Installation

To install this skill, use your terminal within your OpenClaw environment:

npx clawhub@latest install persona-docs

Use Cases

• Project Inception: Before writing a single line of code, use this skill to document who your product is for, preventing feature creep later.
• Team Alignment: Use it to reconcile disagreements among developers or product managers regarding the primary target audience.
• Onboarding Documentation: When bringing new engineers onto a project, this skill provides immediate context on the 'who' and 'why' of the software, accelerating their productivity.
• Feature Planning: Validate that your roadmap matches the pain points identified in your persona documents.

Example Prompts

1. "Create a detailed persona document for my new CLI tool designed for site reliability engineers who struggle with log analysis during production outages."
2. "Review the current codebase in this directory and suggest three primary user personas that best fit the current implementation logic."
3. "Draft a user journey map for a first-time developer landing on my project's website, focusing on their friction points during installation."

Tips & Limitations

• Start Minimal: Do not over-engineer your first draft; a few specific, punchy sentences about the user are better than a vague five-page report.
• Iterate Often: As you receive user feedback or usage metrics, revisit your persona docs to ensure they stay accurate to your actual user base.
• Avoid Vague Labels: Never use terms like 'Developers' or 'Users'. Be specific about their technical skills, environmental pressures, and typical workflows.
• Limitation: The skill relies on input data. If you provide it with an empty codebase and no context, the persona docs will be generic. Always feed it existing project documentation or README files for the best results.