claude-kit: Spec-First Interviews

    1

    Turn a feature idea into a reviewable specification with focused interviews, clear scope, and acceptance criteria you can verify before implementation.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    claude-kit: Spec-First Interviews

    Example session with this skill installed

    Use the spec-first interview workflow for a dark-mode toggle. Interview me about behavior and scope before writing the spec.

    Illustrative example below assumes the interview establishes a light default, local persistence, and no account sync.

    • Read your context and instructions
    • Compiled the claude-kit

    Illustrative deliverable

    This is an example of the complete spec format, not a recorded execution or benchmark.

    Spec: Dark-mode toggle

    Date: 2026-10-29
    Status: draft

    Summary

    Add a light/dark theme toggle in Settings. Save the choice on this device so the next visit uses the selected theme.

    User experience

    The user opens Settings and selects Light or Dark. The page updates immediately. On reload, the saved choice is restored before the main content renders. If storage is unavailable, the current session still switches themes. The initial default is Light.

    Acceptance criteria

    • Settings exposes a keyboard-operable Light/Dark control with a visible label and selected state.
    • Changing the control updates the page without a reload.
    • Reload restores the saved theme.
    • Storage failure does not prevent switching themes for the current session.
    • Navigation and settings remain readable in both themes.

    Out of scope

    • Account synchronization
    • Scheduled theme changes
    • Automatic operating-system theme detection

    Technical notes

    Use the existing settings surface and theme tokens. Store only the theme choice locally.

    Open questions

    None after the assumed interview decisions above.

    Next step

    Review this draft and request corrections. After approval, set Status to approved and invoke the task skill with the saved spec path.

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

    About this skill

    From idea to an approved spec

    Use /spec <feature idea> to turn an underspecified request into a written specification before implementation starts. The skill reads relevant project context, asks focused questions about behavior, edge cases, scope, and success, then writes docs/specs/YYYY-MM-DD-<slug>.md.

    What you get

    • A concrete user-experience walkthrough
    • Independently verifiable acceptance criteria
    • Explicit out-of-scope decisions
    • Technical constraints and unresolved questions
    • A review loop that waits for your approval before handoff

    This package contains the original spec/SKILL.md from Bradley Brewington’s claude-kit. It is an instruction-based workflow for Claude Code, not an executable application. It does not implement the feature. Pair it with the separate claude-kit task skill to execute the approved spec.

    Source: https://github.com/BradleyBrewington/claude-kit

    Agensi delivers text instructions through MCP. Ask your agent to use the spec workflow; the original /spec shorthand refers to the separately installed Claude Code skill. This listing does not install slash commands, shell profiles, or global configuration.

    Requires an interactive Q&A session. Does not perform the actual code implementation. Assumes a local file system for saving markdown specs.

    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

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 19 days ago

    Permissions

    Read Files
    Write Files

    Reads relevant project files and existing specs; writes a specification under docs/specs/. No external account or network service is required by this skill.

    Listed19 days ago

    What's inside

    Frequently Asked Questions

    It provides a repeatable process: read relevant project context, interview the user, write verifiable acceptance criteria and scope boundaries, and ask for review before handing off implementation. Results still depend on the model and the context available.

    The original skill targets Claude Code and its AskUserQuestion tool. Through Agensi MCP, an agent needs local file read/write access and a way to ask interactive questions; other agents may need to adapt the tool name. Compatibility has not been independently tested across every agent.

    No template setup is required. The skill tells the agent to create docs/specs/ if needed. PRODUCT.md is optional. Agensi delivers the instructions via MCP; it does not install a local /spec slash command.

    No. The workflow stops after the spec is reviewed and approved. Implementation is a separate step, using the task skill or your own process.

    A Markdown specification with a summary, user-experience walkthrough, verifiable acceptance criteria, out-of-scope decisions, technical notes, and unresolved questions.

    It is intended for non-trivial features or product ideas, especially work expected to exceed roughly 30 minutes. Small, straightforward changes may not need the interview.

    New in Technical Documentation