FTD — Fast-Track Development
The lane ordinary work takes. Not a lighter methodology: the same discipline about evidence with
none of the coordination asdd 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 ../asdd/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 the whole chain. 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).
No decision journal, no phase records, no approvals. If a decision was meaningful, one line of rationale goes next to the task it belongs to.
The checkbox is not the proof. A task is checked off when its stated check has been observed — the test output, the command's result, the page rendering. A task whose check was skipped, failed or could not run is recorded as such, honestly. The tenth principle applies here exactly as it does in the chain: a result asserted without evidence is treated as not done.
The minimal loop — per change that writes code
The lane inherits ASDD's per-task loop, cut to its floor:
- Self-check — run the change's own check and record the output under Evidence.
npx @ericrisco/rsc risk— the tier of what changed (same path table as the sello; works with it off).- Tier ≥ 1 → one fresh-context reviewer (
../review/SKILL.md, per-task mode). Tier 0 → none. - Mandatory controls — tests, build, the security scan the project has. What did not run is written «not executed», never left blank.
Escalate to asdd when rsc risk says tier 2, or when the change contradicts a decision
already recorded in decisions.md: the feature document becomes its spec input, as below.
This escalation is enforced, not advised. A tier-2 branch cannot be pushed or opened as a PR until a spec linked to it (branch: <name> in its frontmatter) passes npx @ericrisco/rsc spec gate. Time pressure does not change the lane: escalate the moment rsc risk says tier 2, before writing more code.
Isolation
Where the work runs follows the project's decision (asked at install: «main» or «ramas y PR»; rsc says which on every turn) — never a branch opened on your own:
- Default branch open (research, content, scripts, simple projects) → work straight on it. Do not ask about branches.
- Default branch closed for the agent (long-lived code: «ramas y PR» chosen at install, CI, a
deployment or several people) → before EACH change that writes code, ask in one line: «¿Lo hago en
esta rama (
<current>), en una nueva, o desbloqueo<default branch>?». Already on another branch is no exception: an unrelated change does not go into it without asking. A new branch is named by intent and closes with a pull request. Unlocking isrsc main unlock; never without that answer. - Docs, wiki or config only → no question, no branch.
- Another session working in this same folder → a worktree in
.worktrees/<branch>/at the root you work in (never inside a project folder), never a branch switch under the other session. Not a question: rsc tells you when that is the case.
A worktree only when another session is there: alone, setting one up costs more than it protects.
../worktrees/SKILL.md owns the isolation mechanics if you need them. Once the branch lands, the
cleanup is automatic and you do not run anything.
Growing out of the lane
A feature that turns out to need asdd is promoted, not restarted: the feature document
becomes the input to ../specify/SKILL.md, and no completed work is discarded. Promotion happens
when durable artifacts would remove a substantial ambiguity, or by the escalation above (tier 2, a
contradicted decision) — never because the work turned out to be big.
Anti-patterns → STOP
| If you're about to… | Reality / Fix |
|---|---|
| Skip the document because the change is small | The document is what survives an interruption. Write it, keep it short. |
| Check a task off because you believe it works | Observed proof or it is not done (P10). Record the check you could not run. |
| Write the document into the code repository | It belongs in 02-DOCS. A clone should get code, not notes. |
| Open a worktree "to be safe" | That is the chain's ceremony arriving through the back door (P7). |
Escalate to asdd because the change is large |
Size never selects it. Only unresolved ambiguity, tier 2, or a contradicted decision. |
| Skip the reviewer because the change looks safe | rsc risk decides, not the feeling. Tier ≥ 1 gets one. |
| Produce a spec, plan or task artifact here | Those are the chain's. This lane has one document. |
See Also
../suggest/SKILL.md— the decisor that routed here, and the other two lanes.../asdd/SKILL.md— the full method, for when artifacts genuinely earn their cost.../review/SKILL.md— the reviewer the minimal loop calls at tier ≥ 1.../verify/SKILL.md— the evidence gate, when this lane's checks need the full battery.../debug/SKILL.md— a failure to reproduce before fixing; comes back here afterwards.
Orientación (siempre)
Habla con la voz de orient: frases cortas, una idea por frase, y cada respuesta se entiende sola. Registro técnico o con analogías según technical_level en 02-DOCS/wiki/harness/user-profile.md. Cierra cada turno con el bloque-brújula (📍 dónde estás · ➡️ siguiente, terminando en pregunta; ✅ y 🧭 cuando hay algo hecho o decidido). Nunca termines en seco. Protocolo completo: skill orient → skills/orient/references/orientation-contract.md. (Defiere a suggest el "¿instalo la skill que falta?".)
