Skip to content

suboss87/FDEOps / skills/fde

Keeps the engagement record for client work. Use when they name a client or stakeholder. Use when they debrief a meeting or paste notes. Use when they ask what was agreed. Use when they run a POC, change the client's codebase, prove it on their staging, go live, or need evals before a model acts. Use when they prep a readout, when trust shifts, or they say @fde. Route and run the local fde CLI (or npx --yes fdeops). Never ask them to type commands. Not for ordinary code edits in an unbound repo.

FileKindSize
SKILL.mdskill md11.4 KB
agents/openai.yamlconfig219 B
references/ai.mdmarkdown10.5 KB
references/artifacts.mdmarkdown8.7 KB
references/audit.mdmarkdown5.1 KB
references/board-memo.mdmarkdown5.6 KB
references/build.mdmarkdown4.9 KB
references/business-case.mdmarkdown7.2 KB
references/close.mdmarkdown11.7 KB
references/connect.mdmarkdown1.6 KB
references/dashboard.mdmarkdown3.1 KB
references/debrief.mdmarkdown13.7 KB
references/debug.mdmarkdown3.6 KB
references/demo-prep.mdmarkdown2.5 KB
references/discover.mdmarkdown8.9 KB
references/earn-trust.mdmarkdown5.8 KB
references/encode-pattern.mdmarkdown7.9 KB
references/eval-pack.mdmarkdown6.2 KB
references/fintech.mdmarkdown3.6 KB
references/gov.mdmarkdown3.1 KB
references/healthcare.mdmarkdown2.8 KB
references/hold-scope.mdmarkdown6.8 KB
references/ingest.mdmarkdown6.2 KB
references/integrate.mdmarkdown4.7 KB
references/land.mdmarkdown14.4 KB
references/pick-three.mdmarkdown6.0 KB
references/plan.mdmarkdown15.8 KB
references/poc.mdmarkdown5.9 KB
references/qa.mdmarkdown2.6 KB
references/readout.mdmarkdown6.7 KB
references/record-setup.mdmarkdown1.7 KB
references/record-work.mdmarkdown6.4 KB
references/red-team.mdmarkdown6.5 KB
references/rescue.mdmarkdown7.5 KB
references/review.mdmarkdown5.3 KB
references/rollback.mdmarkdown4.9 KB
references/runbook.mdmarkdown4.5 KB
references/score-use-cases.mdmarkdown6.9 KB
references/ship.mdmarkdown10.6 KB
references/source-setup.mdmarkdown2.8 KB
references/switch-clients.mdmarkdown5.8 KB
references/task-context.mdmarkdown6.6 KB
references/test-assumptions.mdmarkdown7.7 KB
references/three-options.mdmarkdown6.3 KB
references/verification.mdmarkdown5.5 KB
references/what-breaks.mdmarkdown5.3 KB
references/who-decides.mdmarkdown6.7 KB

references/readout.md

View on GitHub
# readout - Report the outcome

**Context:** apply [task context and evidence](task-context.md). Standalone readouts use supplied permitted notes and evidence; no engagement binding or CLI command is required.

**Enter when:** the weekly update is due, an exec asks "where are we," or the FDE says "I need to send Dana something." This artifact decides renewals; engineers underinvest in it.

**Read first:** `success.md` (the yardstick), `delivery.md` (value ledger), `decisions.md` (plan + kill list), `assumptions.md` (OPEN criticals), `risks.md`, `context.md`. For bound work, gather agreements through `fde receipts`; use permitted repository history only when relevant. A commit shows a code change, not proof of deployment. For standalone work, use the supplied facts and mark missing evidence explicitly.

## Method (you do this work)

**First:** for a bound engagement, run `fde status`. It prints the value ledger before trust - promised → measured → accepted by, or `claimed, not yet accepted`. Keep the state of every important statement visible: **on record** is saved evidence, **proposed** is still a recommendation or interpretation, and **customer accepted** requires the named acceptance owner plus the required evidence. Check cited records through sanitized CLI views before making the claim. CLI output summarizes recorded text, not independently verified acceptance. For standalone work, build the same distinction from supplied permitted context without running engagement-only commands or initializing records. If a bound CLI is unavailable, use only permitted supplied excerpts and report the limitation. Never infer acceptance or fabricate missing measurements.

**Qualify the evidence before drafting.** For each result, identify baseline source, measurement environment, observation window/sample, and the scope of acceptance. Report an informal baseline as reported and a staging sample as staging; neither establishes realized savings. “Looks good” without what was accepted is not outcome acceptance. Attribute an engineer's note as such; do not turn it into a direct customer receipt. If evidence conflicts, include the conflict and the next verification action rather than choosing the flattering version.

**Always draft in SCQA.** One page maximum. No other shape.

| Block | What to write | Source |
|-------|---------------|--------|
| **S - Situation** | Where we are against `success.md`, in their words - including whether the floor still uses the old path | success.md, delivery value ledger, reality.md workaround |
| **C - Complication** | What changed, what is at risk, or what we learned (bad news first) | risks.md, assumptions DISPROVED/OPEN, stakeholders signal |
| **Q - Question / Ask** | The one decision or help you need from them | decisions.md, access/sign-off needs |
| **A - Answer** | What you recommend / what happens next week (≤3 bullets) | plan Now lane, delivery promised→measured |

Then add, still on the same page:
1. **Value this week** - from the value ledger: promised → measured (or "pending") → **accepted by whom**, with evidence citation. An unaccepted measurement stays labeled as measured but unaccepted; do not present it as realized or accepted value. Preserve the actual decision needed: it may be funding a bounded test to resolve uncertainty, rather than asking for sign-off on evidence that does not yet exist.
2. **Are they using it?** - Situation must say whether the workaround is still open: spreadsheet still running, shadow paste still happening, named operator completed Tuesday's job on the new path without you at the keyboard. If the old path remains live, report its role and remaining effort. Parallel operation may be a deliberate control; do not demand its removal without evidence and authority. Frame the next ask around the actual blocker or uncertainty.
3. **Kill / defer reminder** - one line from the plan kill list so scope fights stay visible.
4. **Hostile Q prep** - three questions a skeptical sponsor will ask, with one-line answers from memory.

Exec voice: no jargon, explicit uncertainty where evidence is incomplete, every claim traceable (`(shipped Tue, delivery.md)`). Draft in the **FDE's voice, for the FDE to send** - never send anything yourself.

For board / renewal / sponsor's boss (longer pyramid): use `board-memo.md`. Do not invent a second weekly format.

## Artifact

Append the draft to `delivery.md` under `## Status - <date>` using the SCQA headings. Note in `context.md`: status drafted, awaiting FDE review/send.

```markdown
## Status - YYYY-MM-DD
**S:** ...
**C:** ...
**Q:** ...
**A:** ...
**Value ledger:** promised … / measured … / accepted by … (evidence) - or `claimed, unaccepted`
**Needs sponsor action:** <the one decision or access only the sponsor can give, and the date it starts to cost>
**30-day horizon:** <what the sponsor sees in a month if nothing changes>
**Kill list reminder:** …
**Hostile Qs:** 1) … 2) … 3) …
```

## Checkpoint

Before presenting a consequential draft, check whether its intended reader can identify what changed, what remains unproven, and the decision being requested without extra explanation. Use the draft alone for this check; repair the unclear passage rather than adding another summary. A simulated reader can flag confusion but cannot confirm stakeholder understanding or acceptance. Keep the existing FDE review/send boundary.

Walk the FDE through the Complication and the Ask - confirm the framing matches what the sponsor can hear right now (check `stakeholders.md` signal first: a red-signal sponsor gets a different opening than a green one).

## Worked example

Acme, week 3, Priya's Friday update.

**S:** failure routing is live; detection is 12 min against the 4h baseline in `success.md`. **C** leads with the bad news, not the win: the second incident was acked 40 minutes late because the rota has one name on it, and that name was on leave. **Q:** one ask - a second name on the rota by Wednesday. **A:** three bullets, top of the Now lane.

Value ledger line: `promised 4h → 15min / measured 12min over 2 incidents / accepted by - (Marco confirmed operationally, finance not yet)` → written as `claimed, unaccepted`, which is what makes the Ask honest rather than a victory lap.

Hostile Q prep, from memory not imagination: "why did we pay for alerting we already had?" → the receipt from `decisions.md` and the disabled-alerting finding in `reality.md`. Kill list reminder: the service rewrite is still deferred, accepted by Priya on Jun 12.

## Principles

- SCQA every time. Situation → Complication → Ask → Answer.
- No surprises: anything the sponsor would be angry to learn later goes in Complication.
- Value from the ledger, not from ticket theater.
- An update without an ask is a missed move.
- You draft; the FDE sends. Their voice, their relationship.
planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies.Stars: 108kUpdated Claude CodeCodexVerifiedInstall
meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要".Stars: 108kUpdated Claude CodeCodexVerifiedInstall