living-docs-navigator

What This Skill Does

The living-docs-navigator is a critical productivity tool for OpenClaw agents that bridges the gap between raw codebase implementation and strategic intent. By standardizing access to the .specweave/docs/internal/ directory, this skill allows the agent to treat internal documentation—such as Architectural Decision Records (ADRs), system specifications, and operational runbooks—as a dynamic source of truth. Rather than relying on static or outdated documentation, the navigator uses precise search utilities like grep and ls to pull relevant context directly from the source. This ensures that every feature implementation or architectural change is informed by existing design patterns, historical trade-offs, and established stakeholder requirements, effectively preventing "architectural drift" and ensuring high-quality, context-aware code generation.

Installation

To install this skill, use the ClawHub command-line interface within your environment:

clawhub install openclaw/skills/skills/anton-abyzov/sw-living-docs-navigator

Once installed, ensure your project directory is structured with a .specweave/docs/internal/ folder to enable the agent to begin indexing and navigating your local documentation suite.

Use Cases

• Feature Implementation: Automatically gather acceptance criteria and user stories before starting a new development task.
• Design Decisions: Cross-reference proposed technical solutions against past ADRs to understand why specific technologies were previously rejected or adopted.
• Incident Response: Quickly locate runbooks and system architecture diagrams to understand how a component fits into the broader ecosystem during an outage.
• Onboarding: Assist developers or agents in understanding the system's governing policies, security standards, and product vision without manual overhead.

Example Prompts

1. "Before implementing the new OAuth flow, find the relevant ADRs in .specweave/docs/internal/architecture/adr/ and summarize the trade-offs mentioned for our current authentication provider."
2. "Search the specs directory for the user stories related to the dashboard widget and provide a brief summary of the acceptance criteria I need to satisfy."
3. "Locate the system architecture document for the payment module to understand how the services communicate, then propose an implementation plan that aligns with our current patterns."

Tips & Limitations

• Proactive Indexing: Periodically run ls commands to confirm file paths before searching, as the agent relies on a consistent directory structure.
• Keyword Strategy: When using grep, use broad enough keywords to catch related documentation, but be specific enough to avoid noise from long technical logs.
• ADR Priority: Always treat ADRs as the highest authority for design; if you find a conflict between your proposed code and an ADR, prioritize the ADR and flag the inconsistency.
• Limitation: This skill is strictly focused on reading local documentation. It does not perform live web searches or external RAG. Its efficacy is directly proportional to how well-maintained your project documentation is.