Forge PRD: Testable PRDs from Ideas or Tickets

    1

    Turn a one-line idea or a vague ticket into a PRD where every acceptance criterion can be checked by a test or a command.

    Free

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Forge PRD: Testable PRDs from Ideas or Tickets

    Example session with this skill installed

    Turn ticket.md into a proper PRD.

    ticket.md:

    Hey, can we get a little command-line habit tracker? Something like habit add "read",
    habit done read and habit streak read. It should remember stuff between runs and
    be pleasant to use. Maybe show a weekly view too. Should work offline obviously.

    • Read your context and instructions
    • Compiled the forge prd

    The ticket has a clear shape but no Non-Goals and several untestable phrases ("pleasant to use", "remember stuff", "weekly view"). Before writing, here are the gaps, all in one message:

    Non-Goals are missing. Proposed: local-only CLI; no accounts, sync, reminders, GUI or analytics beyond the requested views.
    2. Failures: how should duplicate or unknown habits behave? Proposed: exit non-zero with a clear error.
    3. Streak: what counts? Proposed: consecutive daily completions ending today; no completion today means 0.
    4. Weekly view: which week? Proposed: current Monday-Sunday, X marks a completed day.
    5.

    "Pleasant to use" can't be checked by a command. Proposed: a documented --help (testable) plus one [manual-check] for wording.

    (User: "all defaults OK")

    Wrote docs/forge/prd/001-habit-tracker-cli.md: 5 user stories, 11 Given/When/Then criteria, Non-Goals, and an Adjustments changelog.

    
    # PRD-001: habit-tracker-cli
    
    ## Goal
    Provide a small offline command-line habit tracker that lets a person add habits, record daily completions, review streaks, and see the current week. Habit data must persist locally between separate command invocations.
    
    ## Non-Goals
    - No user accounts, authentication, cloud sync, or multi-device sharing.
    - No reminders, notifications, or graphical user interface.
    - No habit scheduling, goals, or analytics beyond daily completions, streaks, and the current-week view.
    
    ## User Stories
    ### US-1: Add a habit
    As a person tracking habits, I want to add a named habit, so that I can begin recording it.
    - AC-1.1: Given no habit named "read" exists in an empty local data store, When I run `habit add "read"`, Then the command exits with status 0, prints a confirmation containing `read`, and a separately started `habit streak read` command exits with status 0 and reports a streak of 0.
    - AC-1.2: Given a habit named "read" already exists in the local data store, When I run `habit add "read"`, Then the command exits with a non-zero status and does not create a second `read` habit.
    
    ### US-2: Record a daily completion
    As a person tracking habits, I want to mark a habit done for today, so that my progress is retained.
    - AC-2.1: Given a habit named "read" exists and the computer date is 2026-10-22, When I run `habit done read`, Then the command exits with status 0, prints a confirmation containing `read`, and a separately started `habit streak read` command reports a streak of 1.
    - AC-2.2: Given no habit named "read" exists, When I run `habit done read`, Then the command exits with a non-zero status and prints an error that contains `read`.
    
    ### US-3: View a habit streak
    As a person tracking habits, I want to see my current streak for a habit, so that I can understand my consistency.
    - AC-3.1: Given the local data store records `read` as done on 2026-10-20, 2026-10-21, and 2026-10-22, and the computer date is 2026-10-22, When I run `habit streak read`, Then the command exits with status 0 and prints `3` as the current streak.
    - AC-3.2: Given the local data store records `read` as done on 2026-10-20 and 2026-10-22, and the computer date is 2026-10-22, When I run `habit streak read`, Then the command exits with status 0 and prints `1` as the current streak.
    - AC-3.3: Given the local data store records `read` as done on 2026-10-21 but not on 2026-10-22, and the computer date is 2026-10-22, When I run `habit streak read`, Then the command exits with status 0 and reports a streak of 0.
    
    ### US-4: See the current week
    As a person tracking habits, I want a weekly view, so that I can see which days I completed each habit.
    - AC-4.1: Given habits `read` and `walk` exist, `read` is recorded as done on 2026-10-20 and `walk` is recorded as done on 2026-10-22, and the computer date is 2026-10-22, When I run `habit week`, Then the command exits with status 0 and prints rows for both habit names, with `X` under the 2026-10-20 column for `read` and under the 2026-10-22 column for `walk`.
    - AC-4.2: Given the computer date is 2026-10-22, When I run `habit week`, Then the output identifies every date from Monday 2026-10-19 through Sunday 2026-10-25.
    
    ### US-5: Use the CLI comfortably
    As a person using the tracker, I want clear command guidance and feedback, so that I can use it without consulting source code.
    - AC-5.1: Given the CLI is installed, When I run `habit --help`, Then the command exits with status 0 and its output documents the `add`, `done`, `streak`, and `week` commands.
    - AC-5.2: Given successful and invalid invocations of the documented commands, When a person reviews their terminal output, Then the wording is clear and concise. `[manual-check]`
    
    ## Constraints
    - The tracker must be usable entirely from a command-line interface.
    - It must store its data locally and retain it across separate command invocations.
    - It must work without network access.
    
    ## Definition of Done
    - [ ] All AC green
    
    ## Adjustments
    - **ID remap:** `habit add` -> US-1; `habit done` -> US-2; `habit streak` -> US-3; weekly view -> US-4; "pleasant to use" -> US-5.
    - **Reformulated:** "remember stuff between runs" -> AC-2.1; "Should work offline" -> Constraints; "weekly view" -> AC-4.1, AC-4.2; "pleasant to use" -> AC-5.1, AC-5.2.
    - **Added:** Non-Goals; duplicate and unknown-habit errors (AC-1.2, AC-2.2); a current-streak definition (AC-3.1 to AC-3.3); Monday-Sunday scope and `X` marker for the weekly view.
    - **Flagged [manual-check]:** AC-5.2.
    - **Dropped:** none.
    

    Next step?
    a) Technical design first (forge-spec, if installed) —

    Recommended: the CLI interface and the on-disk data format need to be agreed before coding
    b) Straight to a phase plan (forge-plan, if installed)
    c) Stop here — the PRD is the deliverable

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

    About this skill

    forge-prd turns a raw idea, or an existing requirements doc, into a PRD that an AI agent can actually build against.

    • Interview mode: asks one question at a time across six topics (goal, non-goals, user stories, acceptance criteria, constraints, definition of done), recommends an answer for each, and writes nothing you didn't confirm. Vague ideas first get 2-3 approaches to pick from.
    • Import mode: maps a Jira/Notion/Linear export or pasted doc onto the same structure, rewrites vague criteria ("should be fast") as Given/When/Then, asks every gap in ONE batched message, and appends an Adjustments changelog so you see exactly what changed.
    • Mandatory Non-Goals, so agents don't drift into scope you never asked for.
    • Stable IDs (US-1, AC-1.2) that plans, tests and commits can reference.
    • Criteria that truly need human judgment get tagged [manual-check] instead of pretending to be automatable.

    No scripts, no network access, no dependencies. Writes one Markdown file (docs/forge/prd/ by default). Stops at an approval gate.

    Requires manual approval at the gate. Untestable criteria are tagged [manual-check] rather than automated. Does not generate code or tests directly.

    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

    Free forever

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 23 days ago

    • Free with an Agensi account

    Permissions

    Read Files
    Write Files

    File Scopes

    docs/forge/prd/**
    docs/context/*.md

    Reads the requirements doc you point it to (and docs/context/lessons.md or memory.md if they exist). Writes one Markdown file under docs/forge/prd/. No shell commands, no network, no environment variables.

    Listed23 days ago

    What's inside

    Frequently Asked Questions

    It replaces vague descriptions with Given/When/Then acceptance criteria and stable IDs (US-n, AC-n.m), ensuring every requirement is binary and verifiable by either a developer or a test runner.

    Yes, the 'Import' mode is specifically designed to ingest messy exports from tools like Jira, Notion, or Linear and normalize them into structured, Markdown-compatible PRDs.

    While the skill is framework-agnostic, it can read your repository's context (like package.json or CI workflows) to ensure the PRD aligns with your existing technical environment.

    You receive the full 'forge prd' skill logic compatible with major AI agent platforms, including the Interview and Import workflows and the standardized PRD templates.

    The skill focuses on defining 'what' needs to be built and 'how' to verify it; it does not write the actual source code or perform the implementation itself.

    The agent will flag criteria that require human judgment (like 'UI aesthetics') as 'Manual,' while focusing the Given/When/Then logic on attributes that can be verified via code or CLI.

    New in Prompt & Skill Engineering