The reusable tool card
If you are starting here, this is the first reusable tool card you write down.
If you already shipped a studio on this path, you already made a tool. This is the card for that shape — skip ahead if the fields already feel obvious.
A reusable tool is not an app.
It is a saved way to do repeated work.
Example: Tracker export → weekly status update.
The tool takes messy input and produces a structured result:
- named outputs
- owners
- open questions
- a follow-up draft
- checks before you trust it
The same shape works for other repeated jobs. Incident notes → runbook entry. Interview scribbles → structured candidate feedback. Different inputs, same move: name the job, fix the output format, write the rules once.
A reusable tool card looks like this:
Tool name:
When to use it:
Inputs it needs:
Rules it follows:
Output format:
Examples:
Checks before trusting:
How to reuse it:
Fill it in now for this job — a couple of rules and an output format are enough — and save it wherever you keep notes. You will run this exact card again later in this chapter.
This is a tool even if it has no code.
It has a job. It has inputs. It has rules. It has an output. It has checks. You can use it again.
And when it misses, the fix goes into the card — a new rule, a new example, a new check — so it does not miss the same way twice.
This matters because the card is what turns a lucky one-off prompt into something a teammate could pick up and run tomorrow without you in the room.
That is building.
Next, fill in a card for this tool — every field, even the ones that feel obvious.
The reusable tool card
If you are starting here, this is the first reusable tool card you write down.
If you already shipped a studio on this path, you already made a tool. This is the card for that shape — skip ahead if the fields already feel obvious.
A reusable tool is not an app.
It is a saved way to do repeated work.
Example: Incident notes → weekly follow-up list.
The tool takes messy input and produces a structured result:
- named outputs
- owners
- open questions
- a follow-up draft
- checks before you trust it
The same shape works for other repeated jobs. Incident notes → runbook entry. Interview scribbles → structured candidate feedback. Different inputs, same move: name the job, fix the output format, write the rules once.
A reusable tool card looks like this:
Tool name:
When to use it:
Inputs it needs:
Rules it follows:
Output format:
Examples:
Checks before trusting:
How to reuse it:
Fill it in now for this job — a couple of rules and an output format are enough — and save it wherever you keep notes. You will run this exact card again later in this chapter.
This is a tool even if it has no code.
It has a job. It has inputs. It has rules. It has an output. It has checks. You can use it again.
And when it misses, the fix goes into the card — a new rule, a new example, a new check — so it does not miss the same way twice.
This matters because the card is what turns a lucky one-off prompt into something a teammate could pick up and run tomorrow without you in the room.
That is building.
Next, fill in a card for this tool — every field, even the ones that feel obvious.
The reusable tool card
If you are starting here, this is the first reusable tool card you write down.
If you already shipped a studio on this path, you already made a tool. This is the card for that shape — skip ahead if the fields already feel obvious.
A reusable tool is not an app.
It is a saved way to do repeated work.
Example: Asset list → campaign ship-list.
The tool takes messy input and produces a structured result:
- named outputs
- owners
- open questions
- a follow-up draft
- checks before you trust it
The same shape works for other repeated jobs. Incident notes → runbook entry. Interview scribbles → structured candidate feedback. Different inputs, same move: name the job, fix the output format, write the rules once.
A reusable tool card looks like this:
Tool name:
When to use it:
Inputs it needs:
Rules it follows:
Output format:
Examples:
Checks before trusting:
How to reuse it:
Fill it in now for this job — a couple of rules and an output format are enough — and save it wherever you keep notes. You will run this exact card again later in this chapter.
This is a tool even if it has no code.
It has a job. It has inputs. It has rules. It has an output. It has checks. You can use it again.
And when it misses, the fix goes into the card — a new rule, a new example, a new check — so it does not miss the same way twice.
This matters because the card is what turns a lucky one-off prompt into something a teammate could pick up and run tomorrow without you in the room.
That is building.
Next, fill in a card for this tool — every field, even the ones that feel obvious.
The reusable tool card
If you are starting here, this is the first reusable tool card you write down.
If you already shipped a studio on this path, you already made a tool. This is the card for that shape — skip ahead if the fields already feel obvious.
A reusable tool is not an app.
It is a saved way to do repeated work.
Example: Export folder → brand-review deck.
The tool takes messy input and produces a structured result:
- named outputs
- owners
- open questions
- a follow-up draft
- checks before you trust it
The same shape works for other repeated jobs. Incident notes → runbook entry. Interview scribbles → structured candidate feedback. Different inputs, same move: name the job, fix the output format, write the rules once.
A reusable tool card looks like this:
Tool name:
When to use it:
Inputs it needs:
Rules it follows:
Output format:
Examples:
Checks before trusting:
How to reuse it:
Fill it in now for this job — a couple of rules and an output format are enough — and save it wherever you keep notes. You will run this exact card again later in this chapter.
This is a tool even if it has no code.
It has a job. It has inputs. It has rules. It has an output. It has checks. You can use it again.
And when it misses, the fix goes into the card — a new rule, a new example, a new check — so it does not miss the same way twice.
This matters because the card is what turns a lucky one-off prompt into something a teammate could pick up and run tomorrow without you in the room.
That is building.
Next, fill in a card for this tool — every field, even the ones that feel obvious.
The reusable tool card
If you are starting here, this is the first reusable tool card you write down.
If you already shipped a studio on this path, you already made a tool. This is the card for that shape — skip ahead if the fields already feel obvious.
A reusable tool is not an app.
It is a saved way to do repeated work.
Example: Ticket export → weekly queue report.
The tool takes messy input and produces a structured result:
- named outputs
- owners
- open questions
- a follow-up draft
- checks before you trust it
The same shape works for other repeated jobs. Incident notes → runbook entry. Interview scribbles → structured candidate feedback. Different inputs, same move: name the job, fix the output format, write the rules once.
A reusable tool card looks like this:
Tool name:
When to use it:
Inputs it needs:
Rules it follows:
Output format:
Examples:
Checks before trusting:
How to reuse it:
Fill it in now for this job — a couple of rules and an output format are enough — and save it wherever you keep notes. You will run this exact card again later in this chapter.
This is a tool even if it has no code.
It has a job. It has inputs. It has rules. It has an output. It has checks. You can use it again.
And when it misses, the fix goes into the card — a new rule, a new example, a new check — so it does not miss the same way twice.
This matters because the card is what turns a lucky one-off prompt into something a teammate could pick up and run tomorrow without you in the room.
That is building.
Next, fill in a card for this tool — every field, even the ones that feel obvious.
The reusable tool card
If you are starting here, this is the first reusable tool card you write down.
If you already shipped a studio on this path, you already made a tool. This is the card for that shape — skip ahead if the fields already feel obvious.
A reusable tool is not an app.
It is a saved way to do repeated work.
Example: Claims spreadsheet → clearance note.
The tool takes messy input and produces a structured result:
- named outputs
- owners
- open questions
- a follow-up draft
- checks before you trust it
The same shape works for other repeated jobs. Incident notes → runbook entry. Interview scribbles → structured candidate feedback. Different inputs, same move: name the job, fix the output format, write the rules once.
A reusable tool card looks like this:
Tool name:
When to use it:
Inputs it needs:
Rules it follows:
Output format:
Examples:
Checks before trusting:
How to reuse it:
Fill it in now for this job — a couple of rules and an output format are enough — and save it wherever you keep notes. You will run this exact card again later in this chapter.
This is a tool even if it has no code.
It has a job. It has inputs. It has rules. It has an output. It has checks. You can use it again.
And when it misses, the fix goes into the card — a new rule, a new example, a new check — so it does not miss the same way twice.
This matters because the card is what turns a lucky one-off prompt into something a teammate could pick up and run tomorrow without you in the room.
That is building.
Next, fill in a card for this tool — every field, even the ones that feel obvious.
The reusable tool card
If you are starting here, this is the first reusable tool card you write down.
If you already shipped a studio on this path, you already made a tool. This is the card for that shape — skip ahead if the fields already feel obvious.
A reusable tool is not an app.
It is a saved way to do repeated work.
Example: Cleaned export → research readout.
The tool takes messy input and produces a structured result:
- named outputs
- owners
- open questions
- a follow-up draft
- checks before you trust it
The same shape works for other repeated jobs. Incident notes → runbook entry. Interview scribbles → structured candidate feedback. Different inputs, same move: name the job, fix the output format, write the rules once.
A reusable tool card looks like this:
Tool name:
When to use it:
Inputs it needs:
Rules it follows:
Output format:
Examples:
Checks before trusting:
How to reuse it:
Fill it in now for this job — a couple of rules and an output format are enough — and save it wherever you keep notes. You will run this exact card again later in this chapter.
This is a tool even if it has no code.
It has a job. It has inputs. It has rules. It has an output. It has checks. You can use it again.
And when it misses, the fix goes into the card — a new rule, a new example, a new check — so it does not miss the same way twice.
This matters because the card is what turns a lucky one-off prompt into something a teammate could pick up and run tomorrow without you in the room.
That is building.
Next, fill in a card for this tool — every field, even the ones that feel obvious.
The reusable tool card
If you are starting here, this is the first reusable tool card you write down.
If you already shipped a studio on this path, you already made a tool. This is the card for that shape — skip ahead if the fields already feel obvious.
A reusable tool is not an app.
It is a saved way to do repeated work.
Example: Tracker export → Q3 roadmap deck.
The tool takes messy input and produces a structured result:
- named outputs
- owners
- open questions
- a follow-up draft
- checks before you trust it
The same shape works for other repeated jobs. Incident notes → runbook entry. Interview scribbles → structured candidate feedback. Different inputs, same move: name the job, fix the output format, write the rules once.
A reusable tool card looks like this:
Tool name:
When to use it:
Inputs it needs:
Rules it follows:
Output format:
Examples:
Checks before trusting:
How to reuse it:
Fill it in now for this job — a couple of rules and an output format are enough — and save it wherever you keep notes. You will run this exact card again later in this chapter.
This is a tool even if it has no code.
It has a job. It has inputs. It has rules. It has an output. It has checks. You can use it again.
And when it misses, the fix goes into the card — a new rule, a new example, a new check — so it does not miss the same way twice.
This matters because the card is what turns a lucky one-off prompt into something a teammate could pick up and run tomorrow without you in the room.
That is building.
Next, fill in a card for this tool — every field, even the ones that feel obvious.
The reusable tool card
If you are starting here, this is the first reusable tool card you write down.
If you already shipped a studio on this path, you already made a tool. This is the card for that shape — skip ahead if the fields already feel obvious.
A reusable tool is not an app.
It is a saved way to do repeated work.
Example: Interview notes → debrief packet.
The tool takes messy input and produces a structured result:
- named outputs
- owners
- open questions
- a follow-up draft
- checks before you trust it
The same shape works for other repeated jobs. Incident notes → runbook entry. Interview scribbles → structured candidate feedback. Different inputs, same move: name the job, fix the output format, write the rules once.
A reusable tool card looks like this:
Tool name:
When to use it:
Inputs it needs:
Rules it follows:
Output format:
Examples:
Checks before trusting:
How to reuse it:
Fill it in now for this job — a couple of rules and an output format are enough — and save it wherever you keep notes. You will run this exact card again later in this chapter.
This is a tool even if it has no code.
It has a job. It has inputs. It has rules. It has an output. It has checks. You can use it again.
And when it misses, the fix goes into the card — a new rule, a new example, a new check — so it does not miss the same way twice.
This matters because the card is what turns a lucky one-off prompt into something a teammate could pick up and run tomorrow without you in the room.
That is building.
Next, fill in a card for this tool — every field, even the ones that feel obvious.
The reusable tool card
If you are starting here, this is the first reusable tool card you write down.
If you already shipped a studio on this path, you already made a tool. This is the card for that shape — skip ahead if the fields already feel obvious.
A reusable tool is not an app.
It is a saved way to do repeated work.
Example: Shift notes → handoff board.
The tool takes messy input and produces a structured result:
- named outputs
- owners
- open questions
- a follow-up draft
- checks before you trust it
The same shape works for other repeated jobs. Incident notes → runbook entry. Interview scribbles → structured candidate feedback. Different inputs, same move: name the job, fix the output format, write the rules once.
A reusable tool card looks like this:
Tool name:
When to use it:
Inputs it needs:
Rules it follows:
Output format:
Examples:
Checks before trusting:
How to reuse it:
Fill it in now for this job — a couple of rules and an output format are enough — and save it wherever you keep notes. You will run this exact card again later in this chapter.
This is a tool even if it has no code.
It has a job. It has inputs. It has rules. It has an output. It has checks. You can use it again.
And when it misses, the fix goes into the card — a new rule, a new example, a new check — so it does not miss the same way twice.
This matters because the card is what turns a lucky one-off prompt into something a teammate could pick up and run tomorrow without you in the room.
That is building.
Next, fill in a card for this tool — every field, even the ones that feel obvious.
The reusable tool card
If you are starting here, this is the first reusable tool card you write down.
If you already shipped a studio on this path, you already made a tool. This is the card for that shape — skip ahead if the fields already feel obvious.
A reusable tool is not an app.
It is a saved way to do repeated work.
Example: Contract clauses → privilege-review memo.
The tool takes messy input and produces a structured result:
- named outputs
- owners
- open questions
- a follow-up draft
- checks before you trust it
The same shape works for other repeated jobs. Incident notes → runbook entry. Interview scribbles → structured candidate feedback. Different inputs, same move: name the job, fix the output format, write the rules once.
A reusable tool card looks like this:
Tool name:
When to use it:
Inputs it needs:
Rules it follows:
Output format:
Examples:
Checks before trusting:
How to reuse it:
Fill it in now for this job — a couple of rules and an output format are enough — and save it wherever you keep notes. You will run this exact card again later in this chapter.
This is a tool even if it has no code.
It has a job. It has inputs. It has rules. It has an output. It has checks. You can use it again.
And when it misses, the fix goes into the card — a new rule, a new example, a new check — so it does not miss the same way twice.
This matters because the card is what turns a lucky one-off prompt into something a teammate could pick up and run tomorrow without you in the room.
That is building.
Next, fill in a card for this tool — every field, even the ones that feel obvious.
no box on this page until now. type below, in your notes app, or paste into your AI tool. park a thought is the same local scratchpad. continue works either way — no sign-in.