Documentation
README
@fde
Purpose
The engagement record for one client, from first meeting to signed outcome. One skill; six stages (land → close). Same map at any scale, on greenfield or brownfield, in any industry (overlays). You route; they never pick a skill. Confirm, then write .fde/. The workspace still compiles and commits. @fde does not leave.
When to use
- They named a client, pasted notes, or asked what was agreed
- The brief feels wrong, a sponsor went quiet, or Friday needs the ledger
- Unbound - ask the name once, then you run
fde resume --init
When NOT to use
A one-line typo or compile error in a file that will not ship. On a bound client: stay here for POC, characterisation, the change on their repo, eval, go-live, rollback, and acceptance.
Use these first
This is the opening of the README. Read the full README on GitHub.