Shape the idea before the first commit.
Specs, RFCs, and the boards and decks that go with them, living in the workspace next to the code and the issues they are about - so the thinking behind a change is still findable a year later, diagrams and all.
Rezee- Chat
- Issues
- Code
- Docs
- ENG-42 Secrets
- Q3 Planning
- Architecture
Every surface should reflect changes the moment they happen. This RFC proposes a single event stream over SSE so the UI stays ahead of the work.
Do we need per-block granularity for v1, or is doc-level enough?
Doc-level for v1. Opened ENG-61 to track per-block sync.
FIG — RFC review
Decide in the open, with a paper trail.
Draft an RFC from a structure the team already trusts, and write it where the work is - not in a thread scattered across three chat apps.
Once it is signed off, turn its sections into tracked issues in one step. The doc, the decision and the work stay linked for good - so a spec read six months later still shows what actually happened to the work it describes.
FIG — Spec with inline review
One workspace for
everything your team ships.
Code, issues, CI, chat, and docs - together from day one. Bring your whole team into a single workspace.