manifest-dev plugin

A skill plugin for agents: work out what is meant first, then record the done criteria and confirm them with evidence.

  • 78 ★ on the repository
  • Last commit
Plugin

Extended access

Why this level

  • The skills write files in the project repository and can create pull requests and tickets in GitHub Issues
All reasons and checks

doodledood/manifest-dev

Install

Manual install

/plugin marketplace add doodledood/manifest-dev

The first of two commands in a Claude Code session.

Access and checks

How we review

Extended accessThe tool runs code or makes network calls and only reads external data.

  • The skills write files in the project repository and can create pull requests and tickets in GitHub Issues

This is third-party code. Review the repository files before installing.

What it does

manifest-dev is a set of free skills for coding agents. `/figure-out` reads code, finds the question that decides the work and asks only what the code cannot say. `/define` writes a Manifest: the outcome, pieces of work, acceptance criteria and global invariants. `/do` builds toward the agreed result and demands fresh evidence for each check, and `/auto` runs all three steps in a row. There are `/setup-project` (a North Star file with the project purpose, a glossary, decision records), a ticket queue (`/ticket-up`, `/next-ticket`, `/run-ticket`) and `/orchestrate` for coordinating an outcome. The work ends in a pull request that shows the change, screenshots or command output at the top.

Who it is for. Experienced developers who hand an agent a large task and want work that is ready for review with minimal rework.

Good fit when

  • The cause of background job failures must be found, and a question comes before a code change.
  • A large piece of work must be described so that its done criteria can be checked.
  • A project runs with an agent for weeks and it needs a purpose, a glossary and decision records.
  • A task queue lives in GitHub Issues and an agent takes items one by one.

Not a fit when

  • The task is small: clarifying and criteria take longer than the edit itself.
  • A quick draft without checks is wanted: the skills spend more tokens and time before building.
  • Fully unattended runs: they spend tokens and you may still reject the result.

Example request

/figure-out why do half my background jobs silently stall?

Limitations

The skills spend more tokens and time before code than a direct request to an agent, and unattended runs spend them on work you may still reject. The tool targets experienced developers. The author states that steady project progress and autonomous business operation through it still need to be proven in use. Claude Code remains the main target and Codex, Pi, OpenCode and Cursor need their own install. The license is MIT.

How to disable. Remove the plugin through `/plugin` in Claude Code or single skills from the skills directory. Manifest files and decision records stay in the project repository.

FAQ

Which skill do I start with?

With `/figure-out`: it investigates a question and recommends a solution but does not start implementing. Then use `/define` and `/do` or straight `/auto`.

What is a Manifest?

A document with the outcome, pieces of work, acceptance criteria and global invariants. `/do` checks them with fresh evidence.

Can skills be installed one at a time?

Yes. Every skill works on its own, for example `npx skills add doodledood/manifest-dev --skill figure-out`.

How do I install for Codex?

With `codex plugin marketplace add doodledood/manifest-dev`. Details are in `dist/codex/README.md`.

What does `/orchestrate` do?

It proposes a plan over the ready tickets of a queue and waits for approval. The `--autonomous` flag lets it act within the assignment without plan approvals.

Discussion

No questions or reviews yet.

Plugins

A plugin marketplace and installer for the full dev loop: task selection, review, cleanup, PRs and releases

PluginBroad access1KRepository stars

A CLI that wires a research-to-delivery pipeline with documents and quality gates into Claude Code, Cursor, Codex and other agents

CLIBroad access280Repository stars

Skills for spec-driven development: brainstorming, planning, debate-style review and idea grilling before the first commit.

PluginExtended access51Repository stars

A 33-skill plugin with gates: question the request, verify facts against sources, test first, review by a second model

PluginExtended access119Repository stars

A plugin with three skills for large development work: project analysis, phased tasks tracked as GitHub Issues, parallel agents and code review

PluginBroad access993Repository stars

agent-toolkit offers generic skills for engineering tasks: from a ticket to a plan, tasks and a handover for review.

PluginExtended access85Repository stars

README in short

The README describes the figure out, define, do path, a project with a North Star, a ticket queue, coordination, token cost and installation for five hosts. It links ADRs and two plugins.

README badge

Report a problem