Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Sdd Flow

    1

    A lean spec-driven development flow that separates planning from execution via a single implementation subagent.

    Free

    1 useSecurity scanned
    sdd-flow

    sdd-flow

    Example session with this skill installed

    /mini-sdd add a new email validation utility to the user service and update the registration flow to use it.

    • Read your context and instructions
    • Compiled the sdd-flow

    I have completed the Mini-SDD flow for the email validation utility. The implementation was handled by the developer subagent following the approved plan, with all verification steps passed.

    Implementation Summary

    PhaseStatusResult
    PlanningSuccess.spec/email-val-service/plan.md created
    DevelopmentSuccess3 tasks completed, 3 commits created
    VerificationSuccessUnit tests passed (0 repairs needed)
    AuditCompletePost-implementation validation verified
    // src/utils/validators.ts
    export const isValidEmail = (email: string): boolean => {
      const emailRegex = /^[^\s@]+@[^\s@]+\.[^\s@]+$/;
      return emailRegex.test(email);
    };
    
    // src/services/user-service.ts
    import { isValidEmail } from '../utils/validators';
    
    export const registerUser = async (data: RegistrationData) => {
      if (!isValidEmail(data.email)) {
        throw new Error('Invalid email format');
      }
      // implementation continues...
    };
    

    Next steps

    1. Review the generated plan.md in .spec/email-val-service/ for the full audit trail.
    2. Run the integration test suite to ensure no side effects in the registration UI.
    3. Merge the feature/email-val-service branch into your main development branch.

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

    About this skill

    Context drift during implementation often leads to agents ignoring safety checks or skipping declared tools. Mini-SDD solves this by enforcing a strict boundary between planning and execution. It uses the Orchestrator for interactive planning and delegates implementation to a clean subagent context, ensuring every safeguard in your plan is actually followed.

    What it does

    • Enforced context separation uses a dedicated subagent for implementation to prevent the agent from skipping tool-fetches or declared skills.
    • Spec-driven planning generates a plan.md artifact that serves as the single source of truth for scope, design, and verification.
    • Automated git management handles feature branch creation, conventional commits for every task, and status tracking.
    • Self-healing verification includes a built-in repair budget of three attempts per feature to fix test failures or linting errors.
    • Resumable workflows check for existing specifications to pick up exactly where a previous session left off without losing state.

    How it works

    1. Initialize the flow by typing /mini-sdd followed by your task description.
    2. Review the plan.md generated by the planning phase and provide feedback or approval.
    3. Monitor as the subagent bootstraps the environment and executes tasks sequentially.

    Frameworks & tools

    This skill is harness-neutral and compatible with Claude Code, Gemini CLI, and Codex CLI. It requires a git-managed repository and an environment capable of spawning subagents.

    Why this beats prompting it yourself

    Manual prompting often results in agents "hallucinating" that they have already performed setup steps or loaded necessary tools. This skill forces a cold-start implementation phase that must explicitly honor the plan's bootstrap contract, resulting in significantly higher reliability for complex refactors.

    Use cases

    • Refactoring a specific module where state isolation is critical for safety.
    • Implementing a small feature that requires atomic git commits for each step.
    • Fixing bugs that require a formal verification and repair loop.
    • Scaffolding new components while maintaining a persistent design spec.

    Known limitations

    The system enforces a maximum budget of three repair attempts per feature. It requires a git repository to function and cannot push, merge, or open pull requests on remote servers.

    Requires git repository. Limit of 3 repair attempts per feature. Implementation is restricted to a single subagent. Cannot push to remotes or manage PRs.

    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 any payment.

    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

    1 use

    Times used to date

    Free forever

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 1 month ago

    • Free with an Agensi account

    Requires

    GitHub
    Google Account
    OpenAI
    Devin
    Digitalapplied
    Medium
    Cursor
    Agentskills
    Python

    Permissions

    Terminal / Shell
    Network Access
    Environment Variables

    Allowed Hosts

    raw.githubusercontent.com
    docs.devin.ai
    www.digitalapplied.com
    codelabs.developers.google.com
    medium.com
    cursor.com
    developers.openai.com
    agentskills.io

    File Scopes

    agents/**
    integrations/**
    scripts/**
    skills/**
    tests/**
    Listed1 month ago

    What's inside

    Frequently Asked Questions

    Mini-SDD separates the planning phase from the execution phase by using a dedicated subagent. This prevents 'context drift,' where an AI might skip safety checks or hallucinate that it has already performed necessary setup steps during a long session.

    This skill is harness-neutral and designed for CLI-based AI environments such as Claude Code, Gemini CLI, and Codex CLI. It requires your project to be in a git-managed repository and an environment that supports spawning subagents.

    No complex configuration is needed; once the skill is added to your environment, you simply initialize it by typing `/mini-sdd` followed by your task. It automatically detects your project structure and existing specifications to begin the planning phase.

    The skill includes an automated self-healing loop that provides a budget of three repair attempts per feature. If a task fails verification or linting, the subagent analyzes the error and attempts a fix before escalating to the user.

    Mini-SDD manages local git operations including feature branch creation and conventional commits for every task. However, for security and control, it does not perform remote actions like pushing code, merging branches, or opening pull requests.

    You receive the full workflow logic and integration scripts compatible with supported CLI agents. Buyers also get access to version updates that improve the repair logic and compatibility with new AI model releases.

    New in Agents & Orchestration