From Agentize
Scans in-repo docs and README to determine architecture documentation depth (Level 0–3) per C3.1 readiness criterion.
How this skill is triggered — by the user, by Claude, or both
Slash command
/agentize:verify-c3-1This skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
<!--
| Level | Description |
|---|---|
| 0 | No in-repo architecture docs |
| 1 | System context documented (users, external systems) |
| 2 | Container/service level documented |
| 3 | Component level documented + critical flows documented |
All documentation must live in-repo or be accessible via MCP to count.
docs/ directory.docs/architecture/).Gather the evidence described above and determine the fulfillment level for C3.1.
Scoring guide:
Report in exactly this format:
C3.1 — Architecture Depth
npx claudepluginhub jaksa76/agentize --plugin agentizeGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Implements work from a spec or tickets using TDD at agreed seams, with regular typechecking and test runs, followed by code review.