Generate and update C4 diagrams and glossary from project documentation.
npx skills add https://github.com/nullhack/pytest-beehave --skill living-docs-nullhack
Please help me install this Agent Skill. Skill: living-docs Source: https://github.com/nullhack/pytest-beehave/tree/main/.opencode/skills/living-docs Command: npx skills add https://github.com/nullhack/pytest-beehave --skill living-docs-nullhack
Generate and update two living documents after a feature is accepted (Step 5) or on stakeholder request: the C4 architecture diagrams and the living glossary, both derived from existing project documentation; no new decisions are made.
Refresh the living C4 diagrams and glossary after a feature is accepted or on stakeholder request.
High-intent search queries and answers about installing and using this skill.
Automate C4 diagram generation by reading discovery, architecture, and completed feature docs to derive context and container markdown files. This keeps diagrams synchronized with project evolution without manual diagramming effort.
Maintain a living glossary by deriving terms from discovery docs, architecture decisions, and completed features. The process extends existing glossary entries rather than overwriting them, ensuring domain terminology stays current.
Keep architecture diagrams in sync by triggering an on-demand read phase after feature acceptance. This updates context and container diagrams using the latest project context and decisions from completed feature files.
You can generate C4 context and container diagrams without modifying original decisions. The process reads existing architecture and discovery files strictly as inputs, ensuring your core architectural records remain immutable.
Update living architecture diagrams and glossary during feature lifecycles for release readiness or on stakeholder request. This ensures documentation reflects current discovery, architecture decisions, and recently completed features.
Diagrams and glossary fall out of sync when maintained manually. Automating extraction from discovery, architecture, and completed feature docs ensures generated context, container, and glossary files match your project state.
CygnusfearCreate modular Obsidian-compatible markdown wikis for project plans.
unfinishablemapGenerate a publish-ready article draft from a topic prompt.
coff33ninjaManage Architecture Decision Records and synchronize documentation with codebase changes.
KrystianYCSilvaCreate Markdown documentation with Mermaid diagrams and GFM tables.
