Company Templates

This directory holds standalone, generically reusable document templates used across ventures and products. Each template establishes structure only — no template in this directory establishes policy by itself. A template becomes a real document (subject to real review and status) only once it is copied, filled in, and given its own front matter with a real document_id, owner, and status.

Index

Template	Use when...
policy-template.md	Writing a company or venture policy — a binding rule, not just guidance.
standard-template.md	Writing a standard — a required way of doing something (format, process, quality bar).
guide-template.md	Writing a guide — recommended practice, not mandatory.
adr-template.md	Recording an architecture/technical decision. Thin pointer to the canonical version at ../docs/decisions/adr-template.md.
venture-brief-template.md	Starting strategy work for a new venture (mirrors ventures/_template/docs/strategy/venture-brief.md).
product-brief-template.md	Starting a new product idea within a venture.
product-specification-template.md	Writing a full product specification, general/company-level version.
feature-specification-template.md	Specifying a single feature in detail.
component-specification-template.md	Specifying a reusable technical component.
data-dictionary-template.md	Documenting the fields/entities a product or component works with.
calculation-specification-template.md	Documenting a specific calculation or formula precisely (esp. for compliance/finance-adjacent logic).
research-brief-template.md	Writing up research findings with sourcing and confidence levels.
test-case-template.md	Writing an individual test case.
test-plan-template.md	Writing a test plan spanning multiple test cases.
release-notes-template.md	Writing release notes for a shipped version.
retrospective-template.md	Running a retrospective after a project, release, or incident.
customer-feedback-template.md	Logging structured customer feedback.
work-plan-template.md	Planning human-facing work; points to ../work/templates/task-plan.md for the AI-agent operational version.

Conventions

• Every filled-in template should carry the document metadata front matter described in the company documentation standard (../docs/standards/document-metadata-standard.md, if present) — title, document_id, document_type, status, owner, etc.
• Never mark a document status: approved as part of filling in a template — approval is a distinct, deliberate step taken by a human owner.
• Templates themselves (the files in this directory) should be marked document_type: template and generally status: draft, since they too are living documents that may be revised.

---

Report an issue about this page