Is FDEOps a fit?

Use it when customer context decides the code.

35 task skills for discovery, delivery and handoff. Use one on its own, or keep an ongoing customer record with fde.

What it adds

Individually installable instructions with explicit inputs, outputs and checks.

Scoped implementation, integration, debugging and verification with your project's tools.

A local customer record and bounded resume output, with targeted retrieval of older evidence.

Separate promises, measurements, sources and recorded acceptance.

Runbook and handoff instructions, including ownership and rehearsal evidence.

A single task

Install one skill and give it the notes or code. No customer record needed.

A continuing customer project

Use fde to select tasks and keep the brief, decisions, evidence and next actions connected.

An existing team setup

Keep your conventions, tests and approved tools. If another skill pack overlaps, select skills by name.

If your own instructions already cover a small, clear task, you may not need FDEOps for it.

Claude Code plugin: Coordinator, individual tasks and session hooks. Hooks use the workspace's customer binding.
Skill-only installation: Selected skills available through the host. No automatically registered Claude Code session hooks.
Workspace adapters: Pointers in supported agent instruction files. They install no model and guarantee no tool access.
Local model with a compatible agent: Depends on the model and the host's file and command tools. Validate on representative tasks.
CLI without an AI model: Local record operations and fieldbook views. No model reasoning.