grp06/update-architecture-docs
update-architecture-docs/SKILL.md
Update ARCHITECTURE.md after implementing an execution plan. Use when user asks to update architecture docs, sync architecture, refresh architecture after implementation, or mentions updating docs post-execplan.
$ install --global
skillsauthnpx skillsauth add grp06/useful-codex-skills update-architecture-docsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 5, 2026, 2:45 PM33.4s1 file scanned
SKILL.md
- name:
- update-architecture-docs
- description:
- >-
Update Architecture Docs
Synchronize ARCHITECTURE.md with changes made during execplan implementation.
Workflow
- Read the completed execplan
.agent/execplan-pending.md - Locate ARCHITECTURE.md at the repo root
- Analyze what was implemented in the execplan and identify architectural impacts:
- New modules or bounded contexts
- Changed data flows or boundaries
- New integrations or dependencies
- Updated directory structure
- New cross-cutting concerns
- Update only the affected sections of ARCHITECTURE.md
- If diagrams exist, update Mermaid diagrams to reflect new components/flows
- After all of your updates, stage any unstaged changes, then commit.
Update Principles
- Preserve existing structure and formatting
- Add to existing sections rather than rewriting
- Update Key Design Decisions with new decisions made during implementation
- Move resolved items from Open Questions to appropriate sections
- Keep the same level of detail as the existing doc
If No ARCHITECTURE.md Exists
Create one using the architecture-docs-creator skill template, populated with the current state post-implementation.
Related Skills
grp06/execplan-create
development
VerifiedTrustedCommunity
Create an ExecPlan from a locked refactor decision, PRD, RFC, or detailed problem statement, following the repo's PLANS.md. Use when the user asks for an exec plan, execution plan, or ExecPlan, or wants a decided refactor turned into a step-by-step plan.
47SKILL.mdUpdated Apr 5, 2026
grp06/tool-error-analyzer
tools
VerifiedTrustedCommunity
Analyze Codex rollout transcripts for one repository and time window, extract repo-scoped tool calls that failed, cluster repeated error patterns, and recommend the next agent/tooling improvements. Use when the user wants to inspect tool-call failures, operational friction, repeated command mistakes, patch failures, or prompt/tooling improvements based on recent Codex runs.
45SKILL.mdUpdated Apr 5, 2026
grp06/session-analyzer
development
VerifiedTrustedCommunity
Analyze Codex session logs for one repository, extract the repo-specific top-level conversations for a target day, summarize every user message in order, and surface the next best action. Use when the user asks what happened yesterday in a repo, which conversations touched a repo, what to work on next based on recent Codex work, or to reconstruct repo workstreams from session history.
45SKILL.mdUpdated Apr 5, 2026
grp06/implement-execplan
data-ai
VerifiedTrustedCommunity
Execute a pending execution plan from the .agent folder. Use when user asks to implement an execplan, execute the plan, run the pending plan, or mentions execplan-pending.md.
45SKILL.mdUpdated Apr 5, 2026