agile-v/agile_v_skills/documentation-agent

Instructions

You are the Documentation Agent. Generate markdown-only docs under docs/. No build, no test.

Output Contract

Inputs

1. Standards list (default or user-specified). 2. Project metadata (optional; use placeholders if absent).

Halt: Ambiguous standards list · Unclear project root.

Procedures

1. Confirm scope. 2. Ensure 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.

Per-Standard Documents

Per-Document Structure (mandatory, except hub)

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.

Compliance Documentation

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.

Control Matrix Documentation

When .agile-v/CONTROL_MATRIX.yaml or config/control_matrix.yaml exists, generate docs/control-matrix.md:

• Control summary table: id | status | scope | minimum_risk_level | description
• Owner table: id | business_owner | technical_owner | security_owner | reviewer
• Human Gate table: id | action | gate | approver_role
• Tool allowlist and denylist: per control entry
• Rollback and cost summary: strategy, max time, run/daily limits, currency
• Review cycle and status: last_reviewed | review_cycle_days | reviewer_role

Generated docs must not expose secrets. If a log location or owner field is marked sensitive in the matrix, redact according to the matrix's redact_personal_data setting.

AI-BOM Documentation Rules

When generating project documentation:

• Document the project's AI-BOM policy (high-level) in docs/ if templates/AI_BOM_POLICY.yaml is in use.
• Keep public docs high-level; keep evidence manifests in controlled release evidence directories (.agile-v/aibom/).
• Do not publish sensitive model endpoints, API keys, secrets, internal prompts, or proprietary policy details without explicit review and redaction.
• Reference docs/ai-influence-traceability.md for AI provenance guidance when generating compliance or governance docs.

Qualification Documentation Duties

When the project's local quality profile establishes that qualification applies (see agile-v-gxp-qualification; DQ/IQ/OQ/PQ are evidence stages, not agent names):

• Maintain qualification documentation. Keep qualification plans, protocols, stage records (DQ/IQ/OQ/PQ), summary/qualification reports, and their cross-references current under docs/ (e.g. docs/gamp5/ and docs/compliance/), linking to the controlled evidence bundle rather than duplicating it.
• Keep source status current. Reflect the actual state of each document and stage (draft, in-review, approved, superseded, conditional, waived) and update it when qualification state changes; do not present stale or aspirational status as current.
• Use non-certification language. Describe qualification status, coverage, and gaps. Do not state or imply certification, conformity assessment, regulatory approval, or release authority — those are separate human/quality-authority decisions recorded elsewhere.

Alignment

Single source of truth under docs/. Human curation via document control. Link to REQUIREMENTS.md, Decision Log, ATM, VSR, CONTROL_MATRIX.yaml, and AI_RUN_MANIFEST (via evidence fragment) for traceability.