Maintain living documentation in docs/ aligned with current architecture and features.
npx skills add https://github.com/acostanzo/quickstop --skill the-monitor
Please help me install this Agent Skill. Skill: The Monitor Source: https://github.com/acostanzo/quickstop/tree/main/plugins/guilty-spark/skills/monitor Command: npx skills add https://github.com/acostanzo/quickstop --skill the-monitor
Keeps the codebase documentation in docs/ aligned with current architecture and feature changes, preventing stale or misleading information from slowing teams.
Initialize and maintain living documentation in the docs/ directory by aligning with architecture and feature templates.
High-intent search queries and answers about installing and using this skill.
To keep codebase documentation accurate, you coordinate living documentation across the codebase by validating the docs/ directory against current architecture and feature templates. This ensures documentation reflects real code changes and prevents stale information from slowing teams.
Validating mermaid diagrams in project documentation involves running validation checks against template-driven workflows that cover architecture and component docs. This process ensures reference templates and diagram support satisfy initialization requirements within the docs directory.
You initialize a docs folder by applying template-driven workflows that generate architecture, feature, and component documentation. This creates a living documentation structure that aligns with the current codebase and supports mermaid diagrams and reference templates.
Template-driven documentation workflows apply specifically to codebases with an existing docs/ directory. Without this directory structure, the initialization, validation, and cleanup lifecycle actions cannot coordinate living documentation or generate reference templates.
Codebase documentation becomes stale when it is not coordinated with ongoing architecture and feature changes. Without living documentation validation that checks the docs/ directory against real code, templates and architecture guidance quickly fall out of sync.
Deep research for architecture documentation is triggered when answering questions about system design requires thorough investigation beyond existing docs. This dispatches dedicated research sentinels to analyze the codebase and validate architectural details.
cliveportmanDefine and enforce documentation conventions for the docs/ directory.
JSai23Update living docs and diagrams after each implementation pass.
kryptonum-devDecompose codebase research questions into parallel sub-agent tasks with file:line evidence.
spencerbeggsAlign design documentation with current codebase architecture and flag unsafe changes.
