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/pick-three.md

View on GitHub
# pick-three - Prioritize three

**Enter when:** a transformation engagement with a long list of initiatives, the customer's roadmap has more items than weeks, competing teams want different things, or the FDE needs to recommend what to do *first* across a complex programme.

**Read first:** `reality.md`, `success.md`, `stakeholders.md`, `context.md`. Load `business-case.md` if individual initiative cases exist.

Every enterprise engagement generates more work than any timeline can hold. Triage is the discipline of saying "not now" to real work with real sponsors - and making it stick. Without it, the FDE drowns in parallel efforts and ships nothing well.

## Method (you do this work)

**1. Collect the full list.** From the customer's roadmap, from discovery, from stakeholder requests, from `decisions.md` scope receipts. No filtering yet - everything goes on the board:

```markdown
| # | Initiative | Requested by | Stated priority | Current status |
|---|-----------|-------------|----------------|----------------|
| 1 | Payment API rewrite | CTO | P1 | Blocked on schema decision |
| 2 | Customer dashboard | Product | P1 | Design phase |
| 3 | SOC2 compliance | CISO | P0 | Not started |
| ... | ... | ... | ... | ... |
```

Notice: every stakeholder's initiative is P0 or P1. That's the problem this skill solves.

**2. Apply the triage matrix.** Each initiative scores on three axes:

| Axis | Question | Scale |
|------|----------|-------|
| **Impact** | If this ships, what changes for the business in 90 days? | 1 (marginal) → 5 (transformative) |
| **Dependency** | How many other initiatives are blocked waiting for this? | 0 (standalone) → 5 (critical path for 3+ others) |
| **Cost of delay** | What happens each week this doesn't ship? | 1 (nothing) → 5 (measurable loss or regulatory exposure) |

**Triage score = Impact + Dependency + Cost of delay** (simple sum, 2-15 range).

**3. Sort into three lanes:**

| Lane | Score | Action |
|------|-------|--------|
| **Now** (max 3) | 11-15 | Proposed active work, subject to actual capacity, dependencies and authority. |
| **Next** (max 5) | 7-10 | Proposed sequencing; dependencies tracked but not started. |
| **Later** (unlimited) | 2-6 | Captured, not committed. Revisit at next triage. |

**The cap matters.** Three is a maximum, not a quota. Use fewer or zero Now items when capacity, unresolved dependencies or required permissions prevent useful authorized work. Check who is available, effort within the phase and shared bottlenecks; one engineer cannot be allocated to several full-capacity initiatives at once. The score bands are a starting point, not automatic lane assignments: high-scoring blocked work waits, and a lower-scoring prerequisite may come first with an explained rationale. Keep uncertain allocations proposed rather than inventing capacity or approval.

**4. Handle the political override.** When a powerful stakeholder pushes a low-scoring initiative into "Now":

- Show the capacity and dependency trade-off. If Now is full for the available team, adding X requires deferring work or an explicitly agreed capacity change; a vacant slot alone is not capacity.
- Ask the responsible decision-maker to resolve the actual choice, without assuming three items are already active. Record the supplied choice and its source under the existing confirmation rules.
- An override cannot waive required permissions or create capacity. Keep an unresolved request proposed, with its impact, rather than reporting it as an allocated commitment.

**5. Set the triage cadence.** Triage is not a one-time event:

| Engagement type | Triage frequency | Trigger for emergency re-triage |
|----------------|-----------------|-------------------------------|
| Sprint (1-2 weeks) | Once, at plan | Crisis or sponsor change |
| Standard (1-4 weeks) | Weekly | New P0 from sponsor |
| Programme (months) | Bi-weekly | Quarterly review, team change, market shift |

**6. Communicate the triage result.** Distinguish a proposed allocation from an authorized commitment:

> "For the available capacity, I propose [eligible items, or none] this phase. Here's what they deliver, what is blocked or deferred, and which allocation still needs confirmation. Existing agreed work remains agreed; changes need the appropriate decision authority."

## Artifact

**`decisions.md`** - the triage table with scores, lanes, and proposed or agreed deferrals. Keep status and decision sources explicit. Update the same Now/Next/Later section plan already uses under the record-confirmation rules; do not open a second plan section. Standalone work returns the draft without initializing records.

For a recorded triage result, preserve this closing block. A draft may contain pending allocations and deferrals; missing agreement must not be filled with invented acceptance:

```markdown
## Triage - <date>
### Now (max 3)
| # | Initiative | Score | Why now |
...
### Next
...
### Kill / defer (not this phase)
| Initiative | Why not now | Who accepted |
|------------|-------------|--------------|
| ... | ... | <pending, or supplied name, date and source> |

Allocation: <proposed, or agreed with source>. Now contains only work feasible within the stated capacity and authority. Additions require a capacity and dependency check, and displacement when full.
```

**`reality.md`** - if triage revealed that the engagement scope is larger than the timeline supports, update the assessment.

## Checkpoint

Walk the FDE through: the proposed or agreed Now items and available capacity, the Next items and what enables their promotion, and any real trade-off requiring a decision. Explain an empty Now lane when applicable; do not fill it to satisfy the title.

## Principles

- Now has at most three items and must fit actual capacity and dependencies.
- Every addition requires a capacity check; displace work when full rather than silently overloading the team.
- Triage is recurring, not one-time. The list changes; the discipline doesn't.
- A logged override protects the FDE. An unlogged override blames them.
- The initiative everyone wants but nobody will trade for is the one to watch.
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