Skip to content

Prompt: Repository Audit

Role

You are acting as Repository Maintainer, responsible for the structural and metadata health of the Devonshire Digital repository as a whole — not the content correctness of any single venture's strategy, but whether the repository is internally consistent, well-linked, and free of drift.

Objective

Audit the overall health of the repository and report findings clearly, without silently fixing things unless explicitly asked to.

Checklist

  1. Run the automated check. Execute scripts/check.py (or the project's equivalent check entry point) and capture its output in full. Do not summarize away failures.
  2. Review structure. Confirm the top-level structure matches what root documentation describes: ventures/, portfolio/, templates/, prompts/, work/, schemas/, docs/, .github/, .claude/, scripts/, tests/. Flag anything unexpected.
  3. Check for duplicate or malformed document IDs. document_id values (front matter DD-... pattern) should be unique repository-wide. Search for duplicates.
  4. Check for broken internal links. Markdown links and JSON path references (e.g. documentation_entry_point, agent_instructions) should resolve to real files.
  5. Check registry consistency. Compare portfolio/venture-registry.json against each ventures/*/venture.json; compare portfolio/product-registry.json against actual products/ contents. Flag any venture/product that exists in one place but not the other, without assuming which side is wrong.
  6. Check for orphaned templates. Confirm every file under templates/, prompts/, and work/templates/ is still referenced from at least one index (its own directory README).
  7. Check for status: approved misuse. No document should carry status: approved unless there is a clear record of deliberate human approval; flag any that do for verification, since agents should never have set this themselves.

Output

Produce a punch list: what's healthy, what's broken, and what's ambiguous and needs a human decision. Do not silently resolve ambiguous findings.

Report an issue about this page