prototype first review checkpoint

    1

    Formalize local prototype reviews with reproducible handoff reports and explicit human approval gates.

    Free

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    prototype first review checkpoint

    Example session with this skill installed

    I've finished the new dashboard layout. Run the prototype checkpoint so I can review it before you start writing the backend tests.

    • Read your context and instructions
    • Compiled the prototype first review

    I have prepared the prototype for the new dashboard layout. The local server is running and the artifact has been verified.

    Status: AWAITING_DIRECTION

    Prototype Handoff: Dashboard Layout

    Decision and Scope: Evaluate the new three-column responsive layout and sidebar navigation. Excludes actual data fetching (uses mock_stats.json) and the user settings modal.

    Artifact:

    • Entry Point: http://localhost:3000/dashboard/preview
    • Build Identity: commit-a7b8c9 (local-changes)
    • Launcher: npm run dev -- --port 3000

    Evidence: Verified div#dashboard-container is present and sidebar links respond to click events in the local browser shell.

    Manual Test:

    1. Role/Data: Use admin-user credentials found in docs/testing-accounts.md.
    2. Action: Navigate to the entry point URL.
    3. Action: Resize the browser window to 768px width.
    4. Action: Click the "Analytics" tab in the left sidebar.

    Expected Result: Layout should collapse to a single column with a hamburger menu; Analytics tab should highlight without page reload.

    Limits: The "Export CSV" button is visible but non-functional. Real-time websocket updates are simulated with static intervals.

    Approval: [Absent - Waiting for human feedback]

    Next steps

    • Access the local URL above to verify the responsive behavior.
    • Provide a clear "Approved" or specific feedback on the layout density.
    • If approved, I will begin hardening the DashboardController and writing unit tests.

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

    About this skill

    Software development often suffers from wasted effort when agents build out complex features before confirming the product direction. This skill enforces a prototype-first workflow, ensuring a usable local change is verified by a human before any production hardening begins. It prevents the common "black box" development cycle by requiring a reproducible, manual test path for every major user-facing change.

    What it does

    • Classifies requests to distinguish between internal maintenance and user-facing product decisions.
    • Defines review slices to isolate the smallest working change that demonstrates a proposed direction.
    • Verifies artifacts by checking local builds, entry points, and specific routes rather than just assuming a server is up.
    • Generates handoff reports containing reachable URLs, specific roles/data needed, and numbered manual test steps.
    • Manages state by tracking whether a change is BLOCKED, AWAITING_DIRECTION, or DIRECTION_APPROVED.

    How it works

    1. Identify the decision by isolating the specific product question that needs human feedback.
    2. Spin up the prototype using isolated local environments and synthetic data to prove the capability.
    3. Run the handoff command to generate a structured report with exact reproduction steps for the reviewer.
    4. Capture explicit approval by recording the human's response and artifact version before proceeding to hardening.

    Frameworks & tools

    This tool works within any local development environment supporting isolated servers and synthetic data. It is compatible with web frameworks (React, Vue, Next.js), API services, and mobile emulators, provided they can be accessed via a local entry point.

    Why this beats prompting it yourself

    Generic prompts often lead agents to skip verification or assume "looks good" is an approval. This skill provides a rigid output contract and state management system that forces the agent to prove the artifact is reachable and functional before it can mark a task as approved.

    Use cases

    • UI/UX Direction when a developer needs to confirm a new layout or interaction flow before writing unit tests.
    • Feature Prototyping to demonstrate a new capability to a stakeholder using local synthetic data.
    • Refactoring Validation to ensure internal changes haven't broken existing user-facing workflows.

    Known limitations

    Does not perform production migrations, credential management, or public deployments. Requires a host environment that allows local server persistence for manual review.

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

    Requires local server persistence for human review. Does not handle production migrations, public deployments, or credential management. UI verification limited to available host browser tools.

    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 13 days ago

    • Free with an Agensi account

    Permissions

    Read Files
    Network Access
    Listed13 days ago

    What's inside

    Frequently Asked Questions

    This skill prevents 'black box' development by forcing the AI to pause and provide a reproducible local test path. It ensures you approve the product direction and UI before the agent spends time (and tokens) on production hardening and complex testing.

    It is compatible with any agent environment that supports local server persistence and file system access. This includes popular web frameworks like React and Next.js, as well as API services that can be accessed via local entry points.

    No, this skill is strictly for local verification. It generates handoff reports for internal review and requires a host environment that allows local server persistence; it does not handle public deployments or production migrations.

    The handoff report is a structured document containing reachable local URLs, necessary login roles or synthetic data, and numbered manual steps for you to verify the change. It serves as a formal bridge between the agent's work and your explicit approval.

    The skill includes a state management system that tracks if a feature is BLOCKED, AWAITING_DIRECTION, or DIRECTION_APPROVED. The agent cannot proceed to the next development phase until it records your explicit approval against a specific artifact version.

    New in Agents & Orchestration

    Free