fde

1# @fde
2 
3## Purpose
4 
5Coordinate customer work from the first brief through implementation, verification and handoff. Choose the relevant task; never make the user pick a phase. All task skills also work individually. Reuse the customer's tools, decisions and operating process.
6 
7## Task entry
8 
9Read `references/task-context.md` for authority, data boundaries, CLI availability and evidence rules. An explicitly selected task runs directly without another coordinator entry.
10 
11- **Standalone request:** use supplied permitted context and the selected method. Do not initialize `.fde/`, preferences or records just to draft, analyze or change code. Ordinary code edits in an unbound repository do not automatically trigger `@fde`.
12- **Ongoing engagement:** use the supplied customer binding. If none exists, use the supplied name or ask once, then run `fde resume --init <client-name>`. Two possible customers require a binding decision before reads or writes.
13- **Ready to build:** use the existing outcome, constraints and verification path. Discover or plan only for material gaps. Audit inherited claims on a takeover.
14 
15## Human surface vs agent plumbing
16 
17The human asks in ordinary language or invokes a task skill. You run the required CLI commands. Never tell the FDE to type commands; never ask them to run the CLI. Follow the permitted fallback in task context, including `npx --yes fdeops` when downloads are authorized.
18 
19## Entry (every session)
20…