Qontak Documents

This is the canonical content repository — it holds only the markdown PRDs, RFCs, and test specs, organized by initiative. It is the single source of truth for product documentation.

All tooling (frontmatter linter, PRD→Jira sync, E2E runner, Docusaurus site, MCP server, Confluence importer) lives in a separate system repo (qontak-docs) and runs against this repo via the DOCS_ROOT env var.

Teams & initiatives

Content is organized <team>/<initiative>/: each top-level folder is a team with a README.md landing page; each initiative is a subfolder with its own README.md and prds/, rfcs/, tests/, and delivery/ subfolders. (The first three hold the product/eng artifacts; delivery/ holds the TPM's program-management docs — timeline, status reports, decision records.) See example-team/example-initiative/ for the expected layout. team and target_quarter are frontmatter fields, never path segments, so a reorg or slipped quarter never forces a git mv.

Authoring

Copy a skeleton from the repo's templates/ folder into the matching subfolder of your initiative, fill in the frontmatter, and open a PR — or use the project-scoped authoring skills under .claude/ (write-prd, score-prd, rfc-starter, rfc-reviewer). CI runs the system linter against this repo, so a copied-and-filled template (or a skill-authored artifact) will pass.