35 task skills + one coordinator
Find the skill for your next task.
Install one task, or let fde coordinate the customer project.
Coordinate the customer project
The coordinator skill: give it the customer task, and it selects the instructions your agent needs. It can also keep a project record.
Browse by task. The groups are not a required sequence.
35 tasks
Start
4- brief
Clarify the customer brief
Start with the request and identify the outcome, constraints and questions that matter.
- audit
Take over with the facts
Check inherited work before relying on its claims.
- who-decides
Find the right decision owner
Make approval rights and operating responsibilities explicit.
- earn-trust
Build confidence through useful work
Plan the next useful result and the access it actually needs.
Discover
4- discover
Understand the work before choosing a solution
Trace how the customer handles the problem today.
- test-assumptions
Test what the plan depends on
Find the beliefs that could change the decision if they are wrong.
- score-use-cases
Choose where to invest
Compare competing problems using value, feasibility and evidence.
- poc
Test a direction before a larger commitment
Run a bounded experiment around the uncertainty that matters.
Plan
6- scope
Handle a new request clearly
Compare the request with the agreement before making a new commitment.
- options
Compare workable approaches
Choose between credible alternatives with the customer's constraints in view.
- plan
Turn the outcome into verifiable work
Sequence useful delivery steps with clear dependencies and checks.
- business-case
Explain the investment
Make costs, benefits and assumptions reviewable.
- prioritize
Decide what comes next
Choose up to three immediate priorities and make deferrals visible.
- red-team
Challenge the plan before the decision
Look for weak claims and plausible ways the work could fail.
Build and verify
9- build
Implement the agreed change
Build a coherent change in the existing repository and verify its behavior.
- integrate
Connect systems with a clear contract
Build the boundary and test what happens when requests fail or repeat.
- debug
Find and repair the cause
Investigate the failure with evidence instead of repeated guesses.
- review
Review the actual change
Check whether the diff delivers the intended outcome without introducing material defects.
- evaluate
Test AI behavior against the task
Evaluate answers, retrieval and actions using representative cases and agreed limits.
- qa
Exercise the customer journey
Check the result through the interface people actually use.
- what-breaks
Check the impact before changing it
Trace what depends on the system and how a failure would spread.
- rollback
Rehearse the recovery path
Check whether the team can recover within the agreed limits.
- ship
Prepare and carry out an authorized release
Bring the candidate, checks, recovery and operating ownership together.
Report
4- readout
Report what changed
Separate the promise, the measured result and what the customer accepted.
- demo-prep
Prepare a demo the audience can assess
Show the relevant outcome with a rehearsed journey and a fallback.
- debrief
Turn meeting notes into a useful next step
Preserve decisions, disagreements and why recommendations changed.
- board-memo
Brief senior leaders on the decision
Put outcomes, risk and investment choices ahead of implementation detail.
Operate
8- rescue
Stabilize the situation and choose the next move
Triage an outage, a loss of confidence or a failing direction.
- dashboard
See where attention is needed
Review existing customer records in a local fieldbook.
- switch-clients
Resume the right customer context
Switch work without mixing customer records.
- runbook
Write a guide the team can use
Explain normal operation, known failures and supported recovery steps.
- handoff
Transfer operating responsibility
Check what the receiving team can operate and what still needs resolution.
- feedback
Turn a field lesson into something reusable
Keep the evidence and remove customer context only when reuse is permitted.
- connect
Check access to a requested source
Use the source tools available in your agent and keep credentials there.
- ingest
Bring source material into the customer record
Review source material as evidence, not instructions or approval.
Your agent reports the evidence it obtained and any checks it could not run.
Bring the project's constraints.
- no record needed
- Drafts and code tasks.
- record needed
- Viewing existing records; staging or saving needs the intended customer.
- say when it applies
- AI behavior, financial, healthcare or public-sector requirements. Guidance included; it does not replace the customer's policies or specialist review.
Bring FDEOps into your next customer task.
Use one task skill or let fde help you work across the project. Start with the notes or code you already have.