Find agent skills by outcome

5. Be honest about problems. Flag technical debt

known issues

Not to scare

but to prepare. If the payment service goes down

someone actually WANTS to read

not something they're forced to.

Education

Explain why decisions were made

what alternatives were considered

4. Be engaging. Use conversational tone

rhetorical questions

- Key URLs (production

staging

post offices

libraries

the technical term afterward

but the reader must understand it first.

- If you ever need to change [X]

be careful because it also affects [Y] and [Z]

- How to run the project locally (step by step

assume zero setup)

Creative

- If I were starting over

I would...

- What it is (one sentence

no jargon)

Education

- Explain external service connections (payments

- If you need to change [X]

you'd update [Y] — but be careful because [Z]

- For each action

walk through the FULL journey step by step:

4. If yes

it sends back a confirmation — the waiter brings the receipt

When a user clicks 'Place Order'

here's what happens behind the scenes:

- For every architectural decision

answer: Why this and not the obvious alternative?

Education

- For each major folder

explain:

- Pick 2-3 core user actions (e.g.

user signs up

Orders come in from the front desk (frontend)

get processed here

[Upload files

provide path

Writing & Content

Write the FORME.md with these sections

in this order:

Coding & Debugging

- My role: [e.g.

I'm the founder / product owner / designer — I don't write code but I make all product and architecture decisions]