ftd

FTD — Fast-Track Development

The lane ordinary work takes. Not a lighter methodology: the same discipline about evidence with none of the coordination the ten-phase chain exists to buy. One document instead of five, written because the work might be interrupted, not because somebody has to approve it first.

You are here because the decisor in ../suggest/SKILL.md ruled that this turn authorises a change and did not select ../sdd/SKILL.md. If it is still a question, you are in the wrong place: go back and answer it.

Why this lane exists

The constitution's seventh principle has said it from the start: «la fricción es proporcional al riesgo. Silencio para lo trivial, ceremonia solo donde el fallo es caro. Un sistema que molesta en el 80% inofensivo acaba apagado, y apagado no protege el 20% que importa.»

The harness spent a long time contradicting it — every request that sounded like building went through ten phases. This lane is that principle finally implemented, not a new idea.

The feature document

One per feature, in the workspace wiki under 02-DOCS/wiki/ftd/<slug>.md. Never inside the code repository: whoever clones it should get code, not somebody else's notes in progress.

It is written before the first change, not after, and it holds exactly this:

---
author: <who asked for it — git user.name>
branch: <the branch the work runs on>
status: in-progress
---
# <feature>

## Intent          — what changes, and why it is worth doing
## Scope           — what is in, and what is explicitly not
## Checklist       — one line per task, each with what would prove it done
## Evidence        — the observed output per completed task
## Next            — the single next step, so an interruption costs nothing

The frontmatter says whose work it is, so «¿qué ha hecho cada uno?» has an answer. You never close it by hand: when the branch lands on the default branch, rsc's post-merge hook sets status: done and replaces Next with where and when it merged (on a closed default branch, via rsc/knowledge).