# Instructions, skills or formats?

Three ways to make the agent work the way your team works, and which one you want.



Plansmith gives you three ways to shape how the planning agent behaves. They look similar from a
distance and they do quite different jobs.

The short version: &#x2A;*instructions are rules, skills are procedures, formats are shapes.**

| Use              | For                                                                                           | The agent reads it                                                  |
| ---------------- | --------------------------------------------------------------------------------------------- | ------------------------------------------------------------------- |
| **Instructions** | Standing decisions it should always follow, like "mobile ships after web, stop proposing it". | Every turn.                                                         |
| **Skills**       | A playbook for a situation: how you write release notes, how you run a readiness review.      | When the situation calls for it, or when you type `/` and pick one. |
| **Formats**      | The shape of the documents it writes, meaning the sections every Spec and Epic has.           | Whenever it writes a Spec or an Epic.                               |

<Callout>
  If you find yourself repeating the same correction in every conversation, that is an instruction.
  If you are explaining a process, that is a skill.
</Callout>

## Why the reading model matters [#why-the-reading-model-matters]

Instructions are injected into **every** turn, so they shape a decision before the agent thinks.
That is why they must stay short, and why they are the right home for a standing rule.

Skills and formats are read **on demand**. The agent only sees a one-line summary of each until it
decides one is relevant, which is why a skill can be long and detailed without slowing every
conversation down.

## Where each one applies [#where-each-one-applies]

All three can be set for the whole company or for a single project, and the narrowest one wins.
Instructions go further: you can also set them just for yourself, or just for one plan.

|                  | You | A plan | Project | Company     |
| ---------------- | --- | ------ | ------- | ----------- |
| **Instructions** | Yes | Yes    | Yes     | Owners only |
| **Skills**       | No  | No     | Yes     | Owners only |
| **Formats**      | No  | No     | Yes     | Owners only |

<Callout>
  **Spec format and Epic format appear in your Skills list, but you edit them under Formats.** They
  are listed there because that is how the agent reaches them.
</Callout>

## Who can change what [#who-can-change-what]

Anything set for the whole company changes every conversation for everyone, so only owners can save
it.

Company instructions go one step further: the agent can **suggest** a change as it learns how you
work, but an owner has to approve it before it takes effect. The agent never writes a skill, at any
level.

<Cards>
  <Card title="Agent instructions" href="/docs/agent-instructions">
    Standing decisions, followed in every conversation.
  </Card>

  <Card title="Skills" href="/docs/skills">
    Playbooks the agent opens when they are relevant.
  </Card>

  <Card title="Spec and Epic formats" href="/docs/formats">
    The sections every Spec and Epic is written to.
  </Card>
</Cards>
