The official Rust RFC (Request for Comments) repository, containing proposals for changes to the Rust language, compiler, and standard library. A great example of how open-source projects use Git-based specification processes.

Repository rust-lang/rfcs Format Markdown Documents 300+
  • Large collection of historical and active RFCs
  • Rich metadata including status, authors, and tracking issues
  • Cross-references between related proposals
  • Long-form technical specifications

The React team's RFC process for proposing substantial changes to React. Shows how a smaller, more focused set of specifications can be effectively managed with Dossiers.

Repository reactjs/rfcs Format Markdown Documents 30+
  • Clean, focused specification format
  • Active and historical proposals
  • Clear status indicators
  • Links to implementation PRs and discussions

What can you build?

These examples show what's possible, but the real power comes from using Dossiers for your own specifications.

Product specifications

Document feature proposals, PRDs, and technical designs. Use pull requests to review and approve specs before implementation begins.

Company policies

Store your employee handbook, security policies, and data governance docs in Git. Track changes and maintain a single source of truth.

Process documentation

Keep release workflows, incident response playbooks, and onboarding guides versioned and accessible to your team.

Architecture decision records

Document technical decisions with ADRs. Maintain a record of why you made certain choices and the alternatives you considered.

Create your own

Whether it's product features, company policies, or architecture decisions — give your documents a beautiful, searchable home.