Agent skill
architecture-extract
Convert raw project structure into clear architectural understanding — module boundaries, data flows, service relationships, and architectural patterns. Activate after codebase-scan during Bootstrap.
Install this agent skill to your Project
npx add-skill https://github.com/Fr-e-d/GAAI-framework/tree/main/.gaai/core/skills/cross/architecture-extract
Metadata
Additional technical details for this skill
- id
- SKILL-ARCHITECTURE-EXTRACT-001
- track
- cross-cutting
- author
- gaai-framework
- status
- stable
- version
- 1.0
- category
- cross
- updated at
- 1772064000
SKILL.md
Architecture Extract
Purpose / When to Activate
Activate:
- After
codebase-scanduring Bootstrap initialization - When architectural understanding is needed before memory ingestion
Process
- Analyze module boundaries and layering
- Identify data flow and service interactions
- Detect architectural patterns (monolith, services, event-driven, etc.)
- Produce a concise architecture summary
Outputs
architecture_insights — concise summary including:
- System structure overview
- Module boundaries and responsibilities
- Key data flows
- Architectural pattern identified
- Major dependencies
- Notable constraints or risks
Quality Checks
- System structure is understandable in one view
- Major dependencies are explicit
- Architecture style is clearly identified
- Output is suitable for ingestion via
memory-ingest
Non-Goals
This skill must NOT:
- Make architectural recommendations
- Propose changes
- Read deeply into implementation details
Converts terrain map into architectural understanding. Feeds directly into memory-ingest.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
ci-watch-and-fix
Watch GitHub Actions CI after PR creation, detect failures, extract logs, apply minimal fixes, and re-push — keeping the delivery session alive until CI resolves or escalating after 3 cycles. Activate immediately after gh pr create and before marking the story done.
qa-review
Validate that implemented code fully satisfies Story acceptance criteria, respects rules, and introduces no regressions. This is the hard quality gate — no pass means no delivery. Activate after implementation is complete.
compose-team
Assemble the context bundles for each sub-agent based on evaluate-story output. Produces spawn-ready packages for Planning, Implementation, QA, or MicroDelivery sub-agents. Activate after evaluate-story, before spawning any sub-agent.
coordinate-handoffs
Validate sub-agent handoff artefacts, sequence phase transitions, and manage retry and escalation logic. Activate after each sub-agent terminates to determine next action.
implement
Generate correct, minimal, maintainable code that satisfies a validated Story's acceptance criteria against an execution plan. Activate when a Story is validated, a plan exists, and all prerequisites are unambiguous.
delivery-high-level-plan
Transform validated Stories into a clear, minimal, governed execution plan. Used by the Planning Sub-Agent as the first planning pass before prepare-execution-plan for Tier 2/3, or as the sole planning output for simple Stories.
Didn't find tool you were looking for?