Analyze session history to update architecture documents in monorepos.
npx skills add https://github.com/etr/groundwork --skill sync-architecture
Please help me install this Agent Skill. Skill: sync-architecture Source: https://github.com/etr/groundwork/tree/main/skills/sync-architecture Command: npx skills add https://github.com/etr/groundwork --skill sync-architecture
Keeps architecture documentation in sync with actual implementation decisions made during sessions, ensuring the team references up-to-date guidance.
Run the architecture-sync skill after a session to update the architecture document with implemented changes.
High-intent search queries and answers about installing and using this skill.
To sync architecture documentation with code changes, analyze session history to identify architectural deviations and new tech choices, then update the architecture docs under your specs directory to reflect implemented decisions.
Updating architecture docs in a monorepo involves analyzing session outcomes to detect component additions and structural deviations, then applying targeted updates to single-file or directory-based architecture structures to maintain alignment.
Detect architectural deviations by reading session data to evaluate implemented decisions against existing architecture documents, identifying new technology choices, structural changes, and deviations from the documented architecture.
Yes, you can automate architecture document updates in multi-project setups by analyzing session history to determine affected architecture sections and applying changes directly to the architecture structures in the specs directory.
You need to run an architecture sync after a development session to ensure architecture documents capture implemented changes, preventing the team from referencing outdated architectural guidance.
Architecture documentation sync supports both single-file and directory-based architecture structures, reading session data to determine affected sections and updating the files under the specs directory accordingly.
phraGenerate implementation walkthroughs documenting decisions, changes, and verification steps from run logs.
retranExtract and link concepts from Confluence pages and Jira issues into a knowledge graph.
RelevanceAISummarize session errors, fixes, and patterns into documentation updates.
zzafergokConvert Markdown documents to HTML using marked.js, pandoc, gomarkdown, or static site generators.
