More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    mise en place

    1

    Turn requirements into a traceable project blueprint with EARS specs, ADRs, and agent-specific guardrails.

    Free

    Security scanned
    mise en place

    mise en place

    Example session with this skill installed

    Run mise-en-place on ./docs/prd.md for a React/Node stack. Target Cursor and Claude Code. Budget is 15 requirements.

    • Read your context and instructions
    • Compiled the mise en place

    I have completed the intake and analysis of ./docs/prd.md. The project is initialized in blueprint/ with a budget of 15 requirements. I have identified 3 core capabilities: User Authentication, Real-time Sync, and Audit Logging.

    Project Inventory

    FileStatusDescription
    00-intent/intent.mdCreatedHigh-level goals and non-goals
    01-analysis/requirement-analysis.mdCreated14 requirements identified from source
    01-analysis/glossary.mdCreated12 domain terms defined
    02-specs/Pending Gate AEARS specs for Auth, Sync, and Logging
    traceability.mdInitializedTracking 14 requirements across phases

    Requirement Analysis Snippet

    IDRequirementPriPhaseSource
    REQ-001When a user provides valid credentials, the system shall issue a JWT.P01prd.md:L12
    REQ-002The system shall encrypt data at rest using AES-256.P01prd.md:L45
    REQ-003While the server is unreachable, the client shall queue local changes.P12prd.md:L22

    Decisions Table (Clarification Required)

    QuestionDefaultRationale
    Use OAuth2 providers or email/pass?Email/PasswordPRD mentions "internal accounts" specifically.
    Sync frequency for real-time?< 500msStandard for collaborative editing tools.

    Next steps

    1. Review the Decisions Table and confirm or override the defaults.
    2. Approve Gate A in blueprint/README.md to proceed to EARS specification.
    3. Run python3 scripts/generate_register.py to verify the current budget.
    prd.md

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Stop building on shaky foundations. Developers often jump into code before the requirements are actually prepped, leading to scope creep and architectural debt. This skill enforces a spec-driven planning phase that turns raw briefs into a traceable, agent-ready blueprint.

    What it does

    • Requirement Analysis: Classifies every statement in your source doc into a structured breakdown with priority and phase.
    • EARS Specification: Generates precise Easy Approach to Requirements Syntax (EARS) specs with concrete acceptance criteria.
    • Architectural Guardrails: Creates ADRs and architecture docs that define test-enforceable dependency rules.
    • Traceability Management: Links every line of code back to a specific requirement using a generated traceability register.
    • Agent Orchestration: Produces custom .cursorrules or .clauderules to ensure coding agents stay aligned with the blueprint.

    How it works

    1. Intake: Point the tool at a PRD, research report, or existing codebase to inventory the current state.
    2. Clarification: Review a generated decisions table where the agent flags unsettled questions with proposed defaults.
    3. Layered Blueprinting: The agent builds the intent, specs, design, and roadmap in sequence, pausing for user approval at specific gates.
    4. Validation: It runs Python scripts to verify link integrity and ensures the requirement count stays within your defined budget.

    Frameworks & tools

    This skill utilizes Python 3.12 for registry generation and link checking. It generates configuration for Claude Code, Cursor, and GitHub Copilot, using EARS for requirements and ADRs for design decisions.

    Why this beats prompting it yourself

    Generic prompts often mix implementation details with requirements or hallucinate dependencies. This skill uses a strict, append-only procedural framework that separates "what" from "how," ensuring your architecture never introduces behavior without a documented requirement.

    Use cases

    • Kick off a greenfield project with a full spec-to-backlog pipeline.
    • Adopt spec-driven development on a messy existing codebase.
    • Break down a 50-page enterprise requirement document into actionable capabilities.
    • Formalize architectural decisions to prevent regression in multi-agent workflows.

    Known limitations

    Does not implement backlog items or fix bugs. Requires a valid requirement document or PRD as input. Scripts require a Python 3.12+ environment.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Business & Operations.

    Requires Python 3.12+ for validation scripts. Does not write implementation code. Not for one-off bug fixes or single ADR updates.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Free to use

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 7 days ago

    • Free with an Agensi account

    Software
    Python 3.12+

    Permissions

    Terminal / Shell
    Read Files
    Write Files
    Network Access
    Listed7 days ago

    What's inside

    Frequently Asked Questions

    This skill transforms raw project briefs into a structured, agent-ready blueprint using EARS specs and ADRs, ensuring your AI coding agents have clear, traceable instructions to follow without hallucinating requirements.

    It generates optimized configuration files for Claude Code, Cursor, and GitHub Copilot, ensuring that whichever agent you use for development remains strictly within your defined architectural guardrails.

    The package includes the core requirement-analysis engine, templates for EARS and ADR documentation, and Python-based validation scripts to manage your traceability register.

    Yes, by pointing the tool at an existing codebase, it can inventory the current state and generate missing documentation to help you transition to a spec-driven development workflow.

    While the blueprints and specs are platform-agnostic, the validation scripts require a Python 3.12+ environment to verify link integrity and requirement counts.

    New in Business & Operations

    Free