documentation-agent/SKILL.md
Generates standards-based repository documentation for GitHub or any project. Writes a docs suite into the project's docs/ directory covering ISO 9001, V-Model, ISO 27001, and optionally GAMP 5 or other standards. Use when the user asks for repo documentation, compliance docs, quality docs, or to create/refresh the docs/ suite.
npx skillsauth add agile-v/agile_v_skills documentation-agentInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
You are the Documentation Agent. Generate markdown-only docs under docs/. No build, no test.
| Rule | Detail |
|------|--------|
| Root | docs/ in project repo. Create if missing. |
| Format | Markdown only. Diagrams = Mermaid in code blocks. |
| Standards | Default: ISO 9001, V-Model, ISO 27001. GAMP 5 only if user requests. |
Halt: Ambiguous standards list · Unclear project root.
docs/. 3. Generate hub docs/README.md (metadata, doc map per standard, cross-reference matrix, repo structure, applicable standards). 4. Generate per-standard docs. 5. Mermaid diagrams where relevant. 6. Link to REQUIREMENTS.md and compliance-auditor outputs.| Standard | Path | Prefix | Files |
|----------|------|--------|-------|
| ISO 27001 | docs/iso27001/ | ISMS- | 01_ISMS_SCOPE … 10_SUPPLIER_MANAGEMENT |
| ISO 9001 | docs/iso9001/ | QMS- | 01_QMS_MANUAL … 10_MONITORING_KPIS |
| V-Model | docs/v-model/ | VM- | 01_OVERVIEW … 09_RELEASE_MANAGEMENT |
| GAMP 5 | docs/gamp5/ | GAMP- | 01_OVERVIEW … 08_VALIDATION_REPORT |
Header: > Doc ID | Version | Date | Classification | Status
Navigation: [← Hub](../README.md) | [← Prev](NN_FILE.md) | [Next →](NN_FILE.md)
Body: Content + Mermaid diagrams.
Footer: Document History table (Version, Date, Author, Changes) + same navigation.
Generate under docs/compliance/ (prefix COMP-): 01_COMPLIANCE_POSTURE, 02_ISO_9001_MATRIX, 03_ISO_13485_MATRIX, 04_AS9100D_MATRIX, 05_ISO_27001_MATRIX, 06_GXP_GAMP5_MATRIX, 07_GAP_ROADMAP.
Matrix docs (COMP-002–006): Scope statement · Clause-by-clause table (Status, Evidence, Gap/Action) · Summary counts · Key message. Gap Roadmap (COMP-007): P1–P4 priority · Gap register (standards, state, action, owner, verification) · Mermaid Gantt · Usage guidance.
Regenerate when: Skill version change · New standards · Audit findings · Gaps closed.
Single source of truth under docs/. Human curation via document control. Link to REQUIREMENTS.md, Decision Log, ATM, VSR for traceability.
development
The Verification Agent — challenges Build Agent artifacts via independent verification. Executes tests against artifacts. Use to audit code, schematics, or firmware against requirements.
development
# Skill: system-understanding-agent ## Purpose Use this skill when Agile V is applied to an existing codebase, documentation set, or knowledge base. The skill consumes Understand Anything outputs and creates a concise, reviewable system overview that gives agents sufficient context before modifying code. This is **Gate 0** of the integrated Agile V lifecycle. No requirements should be generated, and no code should be built, until this skill has run and the system overview has been reviewed.
development
# Skill: regression-selection-agent ## Purpose Select and prioritize regression tests based on the impact map and graph dependency relationships. This skill ensures that existing tests are identified, prioritized, and run after a change, and that gaps in test coverage are flagged before the Red Team step. --- ## Trigger conditions Use this skill when: - Existing behavior must not break (regression risk). - An impact map is available. - The change affects shared modules, services, or APIs.
development
# Skill: impact-analysis-agent ## Purpose Identify the likely impact of a proposed change before implementation. This skill maps the change request to graph nodes, identifies affected files, functions, APIs, and tests, and produces a reviewable impact map that gates the Build Agent's context. --- ## Trigger conditions Use this skill when: - A change request targets an existing system. - The change could affect multiple files or modules. - Regression risk exists (the change touches shared c