define

Generate a Manifest with Deliverables, Acceptance Criteria, Invariants, and verification steps.

70|9|Updated Jan 27, 2026
One-click install
npx skills add https://github.com/doodledood/manifest-dev --skill define-doodledood
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: define
Source: https://github.com/doodledood/manifest-dev/tree/main/claude-plugins/manifest-dev/skills/define
Command: npx skills add https://github.com/doodledood/manifest-dev --skill define-doodledood

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Define skill helps teams capture everything that must be built by translating raw needs into a complete Manifest. It creates Deliverables with explicit Acceptance Criteria, documents the Invariants that constrain the work, and prescribes verifiable methods to confirm success.

Core Features & Use Cases

  • Generate a comprehensive Manifest that comprises Deliverables, Invariants, and verification criteria.
  • Proactively surface latent requirements through domain grounding, risk analysis, and pre-mortem scenarios.
  • Provide clear, testable criteria and a verifiable process that guides execution and validation.

Quick Start

Provide a task description and context, and I will generate a comprehensive manifest with deliverables, invariants, and verification criteria.

Frequently Asked Questions about define

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I define deliverables with acceptance criteria for complex multi-repo tasks?▼

To define deliverables for multi-repo tasks, generate a comprehensive Manifest containing explicit Acceptance Criteria, Invariants, and verifiable methods. This translates raw needs into structured constraints and prescribed validation steps to confirm success.

What is a deliverables manifest and when do I need invariants and verification steps?▼

A deliverables manifest is a structured record of work items constrained by invariants and validated by verification steps. You need this when managing complex, multi-skill tasks requiring explicit risk analysis, domain grounding, and testable acceptance criteria.

How do I surface latent requirements using pre-mortems and backcasting?▼

Surface latent requirements by applying pre-mortem scenarios and backcasting to proactively identify project risks and domain-grounding needs. This process exposes hidden constraints early, ensuring the final manifest captures comprehensive deliverables and invariants.

Can I use this manifest approach for multi-skill scope planning and risk analysis?▼

Yes, you can use manifest generation for multi-skill scope planning and risk analysis. It applies domain grounding, pre-mortems, and backcasting to complex tasks, ensuring structured deliverables, verifiable constraints, and explicit verification methods for each criterion.

Best way to translate raw needs into testable acceptance criteria and verifiable constraints?▼

The best way to translate raw needs into testable acceptance criteria is by generating a structured manifest. This defines explicit deliverables, documents constraining invariants, and prescribes verifiable methods to confirm execution success.

What are the limitations of using a manifest for multi-repo deliverables and domain grounding?▼

The manifest approach is limited if your task lacks raw context or domain grounding inputs. Without providing a task description and context, generating comprehensive deliverables, accurate invariants, and verifiable constraints for complex multi-repo scenarios is not possible.