citationslisted

# Citations Standard citation format for maintaining source traceability across all document types. Designed to be readable by both humans and LLM agents processing documents downstream. This skill defines the convention. It is referenced by other skills (pm-spec, research, project-management, etc.) that produce documents with source citations. > All examples below are illustrative. Names, URLs, and quotes are fabricated to > demonstrate the format — substitute your own sources. --- ## Footnote Format Use markdown footnotes. Every significant claim gets a footnote. **Inline reference:** ```markdown Support agents currently search the knowledge base manually after each call[^call-workflow]. ``` **Footnote definition (at document end):** ```markdown [^call-workflow]: Product planning meeting, 2026-01-15. J. Rivera (PM), A. Okonkwo (Eng). "After a call ends, the agent has to go dig through the knowledge base themselves." [View Thread](https://example.slack.com/archives/C00000000/p0000000000000000) ``` ### Footnote Naming Convention Short, descriptive slugs: `[^org-topic]` or `[^topic-subtopic]` - `[^call-workflow]` — post-call workflow description - `[^vendor-sla]` — vendor SLA terms - `[^rivera-scope-v1]` — Rivera's v1 scope decision (see the Meetings example below) - `[^platform-dns]` — DNS discussion in #platform ### Required Components Each footnote must include what's available from the source: 1. **Source context** — what kind of source (meeting, Slack thread