Technical decisions your team and AI agents can build on.

From an open question to a decision everyone can reuse.

One illustrative example, followed from discussion to code. Not a customer.

1. 1

   Discuss a problem.

   A problem is a question your team has to answer. Its options, For and Against arguments, evidence and comments sit in one place. An AI review points out unstated assumptions, contradictions and options nobody weighed, and cites what it read.

   PRB-142

   Add a Redis cache to the orders service?

   Options

   • Add a Redis cache2 for·2 against
   • Add a Postgres read replica1 for·1 against

   AI reviews the room and cites what it read

   Contradiction“No new infrastructure this quarter” conflicts with the Redis option.

   Decided Decided by the team

   No Redis in this service. Index the order lookups first; revisit if p95 stays above 200 ms.

   See the full example

   • Assumption“Reads are the bottleneck” — no load data in the evidence yet.Description
   • Contradiction“No new infrastructure this quarter” conflicts with the Redis option.ArgumentOption
   • SuggestionNot weighed yet: index the order-lookup queries.Description

   AI points out what to check and spends credits when it runs. A person on your team makes the call.

2. 2

   Record the decision and why.

   A person on the team records what was chosen, which options it beat and why, and when to reconsider it. Ask why months later and the answer comes back with its reasoning, from any team in the workspace.

   Why don't we use Redis?Search by meaning

   PRB-142 Decided

   No Redis in the orders service

   Chosen

   Index the order lookups first.

   Not chosen

   Redis cache: no new infrastructure this quarter. Read replica: the slow part is the query, not the load.

   Revisit if

   p95 stays above 200 ms.

3. 3

   Give your coding agent the context.

   The agent can look up what your team decided and why, instead of proposing an option you already ruled out.

   Connect Rationode to your agent over MCP, or download the Agent Pack and add its files to your repository.

   How agents get the context

   • Over MCP, the agent asks Rationode while it works and always gets the current published pack and decisions.
   • Downloaded files are a snapshot. After the pack is published again, download it again.
   • A change is checked against your decisions when the agent calls check_changes. The Claude Code plugin asks it to at the end of a turn, or you can ask it yourself.

   • You Speed up order lookups in the orders service.
   • Coding agent I looked up your team's decisions. PRB-142: don't introduce Redis in this service — no new infrastructure this quarter. I'll index the order lookups instead.
   For developers: skills, Agent Packs and delivery

   You choose what each team's agents receive and publish it as an Agent Pack.

   • A decisionRecords one choice the team made and why. An agent reads it as a rule.PRB-142 · No Redis in the orders service. Index the lookups first.
   • A skillReusable guidance on how this team does a kind of work, wherever it comes up.api-contracts · Additive changes first. Existing clients keep working.

   1. 1Skill library

      Write a skill once, for every team.

      ---
      name: api-contracts
      description: Use when changing a
        request or response shape.
      ---
      - Prefer additive changes: add
        optional fields, never rename.
      - Keep existing clients working
        through a migration: serve the
        old and new shape side by side.
      - Remove a deprecated field only
        after its consumers have moved.

      AI can suggest a sharper draft or flag a clash with a recorded decision. The author applies it or discards it.

   3. 2Agent Pack · Orders team

      Put it in a team's pack, beside its decisions.

      • Rule · from Shared packPRB-142 · No Redis in the orders serviceAsked: Add a Redis cache to the orders service?
      • Skill · from Shared packdb-migrations
      • Skill · from Orders teamapi-contracts

      A curator picks which decisions and skills go in, then publishes; publishing freezes the wording. Every team pack includes the Shared pack.

   5. 3Coding agents

      Your agents receive the published pack.

      • .claude/skills/api-contracts/SKILL.md
      • .claude/skills/db-migrations/SKILL.md
      • .claude/skills/rationode-prb-142/SKILL.md

      One Agent Skills folder per rule and skill, for .claude/skills and .agents/skills.

   Writing skills and building packs is free. Free delivers a pack of up to 3 decisions and 3 skills; larger packs come with Team.