Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    PRD Architect

    1

    Standardized PRD generator using ISO 29148, MoSCoW, and INVEST to create review-ready software requirements.

    $9

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    PRD Architect

    PRD Architect

    Example session with this skill installed

    Draft a PRD for a mobile pet-health app. Features: vaccine reminders, health records, vet chat. Target users: young pet owners. Include prioritization and NFRs.

    • Read your context and instructions
    • Compiled the prd architect

    I have generated a complete PRD for the pet-health app, including 5 functional requirements with business rules, ISO 25010 non-functional requirements, and a quality self-audit.

    PetHealth Mobile App Product Requirements Document (PRD)

    Document Information

    • Title: PetHealth Mobile App PRD
    • Version: v1.0
    • Status: Draft for Review

    1. Functional Requirements

    FR-001: Vaccine Reminders

    • Priority: M (Must)
    • Kano: Must-be

    User Story: As a pet owner, I want to receive push notifications for upcoming vaccinations so that my pet stays healthy and compliant with local laws.

    • Deep Description:

    Business Rules: Reminders trigger 7 days, 3 days, and 24 hours before the due date. Users must be able to mark a vaccine as "Completed" which auto-schedules the next dose based on frequency data.

    • Error Flows: If notification permissions are denied, show an in-app banner on the dashboard.
    • Boundary Conditions: Support up to 20 pets per account; reminder titles max 50 characters.
    • Acceptance Criteria:
      • Given a vaccine is due in 7 days, When the system clock reaches 09:00 local time, Then a push notification is sent to the user.
      • Given a user taps "Completed", When the vaccine type is "Rabies (1-yr)", Then a new reminder is created for 365 days from the completion date.

    FR-002: Real-time Vet Chat

    • Priority: S (Should)
    • Kano: Attractive

    User Story: As a pet owner, I want to chat with a verified vet, so that I can get immediate advice for non-emergency issues.

    • Deep Description:

    Business Rules: Session starts only after user accepts the "Not for emergencies" disclaimer. Chats are archived after 24 hours of inactivity.

    Error Flows: If no vet is available, show "Average wait time: X mins" and allow user to leave an offline message.

    • Acceptance Criteria:
      • Given an active session, When a vet sends a message, Then the user receives a real-time notification and the message appears in the thread within <1s.

    2. Non-Functional Requirements

    IDCharacteristicMetricTest Method
    NFR-001PerformanceChat message delivery < 500msWebSocket latency test
    NFR-002SecurityAll health data encrypted at rest (AES-256)Security audit / DB inspect
    NFR-003Availability99.5% uptimeMonthly status monitor

    3. SRS Quality Self-Audit

    • Structural Completeness: 20/20
    • Requirement Clarity: 23/25 (-2 for vague "real-time" definition in chat)
    • Prioritization: 20/20
    • Verifiability: 20/20
    • Traceability: 15/15
    • Total Score: 98/100 (Pass)

    Next steps

    1. Review the Open Questions regarding the vet verification process.
    2. Approve the MoSCoW priorities for the initial sprint.
    3. Pass the NFR metrics to the DevOps team for infrastructure calibration.

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

    About this skill

    Requirement gathering is often messy, vague, and inconsistent. This skill converts raw product ideas into review-ready PRDs compliant with ISO/IEC/IEEE 29148:2018 standards.

    What it does

    • ISO Standard Structuring generates complete document metadata, glossaries, and requirement matrices following ISO 29148.
    • Functional Requirements creates numbered FR-XXX entries including INVEST user stories, MoSCoW priorities, and Kano classifications.
    • Deep Logic Definitions specifies business rules, explicit error flows, and boundary conditions for every feature.
    • Acceptance Criteria writes testable Given-When-Then (BDD) scenarios for all functional requirements.
    • NFR Benchmarking provides quantified non-functional requirements based on ISO 25010 quality characteristics.
    • Quality Auditing executes a five-dimension weighted self-audit to score the document on clarity and verifiability.

    How it works

    1. Provide the product name, target users, and core problem or feature list.
    2. The agent identifies missing information and uses industry-default fallbacks marked for confirmation.
    3. It generates the full PRD including ASCII or Mermaid flow diagrams for complex logic.
    4. Review the Requirements Traceability Matrix (RTM) and the quality self-audit report.

    Frameworks & tools

    This skill implements ISO/IEC/IEEE 29148:2018 for systems engineering, ISO 25010 for software quality, MoSCoW for prioritization, Kano for satisfaction modeling, and INVEST for user story validation.

    Why this beats prompting it yourself

    Standard prompts often miss critical edge cases like error flows and boundary conditions. This skill enforces strict industry standards and produces a traceability matrix, ensuring every requirement is actually testable and aligned with business value.

    Use cases

    • Product Kickoff turning a one-sentence pitch into a full MVP requirements document.
    • Feature Iteration drafting detailed logic for a new module within an existing app.
    • Requirement Cleanup standardizing vague stakeholder requests into structured technical specifications.
    • Audit & Review scoring existing PRDs against ISO standards to identify gaps in logic or verifiability.

    Known limitations

    Does not produce visual wireframes or UI designs. Technical architecture, database schemas, and API specs are out of scope. Performance metrics are reference baselines and require engineering validation.

    No visual wireframes or architecture diagrams. No live market research or API specs. NFR metrics are reference baselines only. Requires user to provide at least product name and target users.

    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 today

    Permissions

    No special permissions declared or detected

    Listedtoday

    What's inside

    Frequently Asked Questions

    The skill transforms vague ideas into structured documents using ISO 29148 standards, ensuring every requirement includes MoSCoW prioritization, INVEST-compliant user stories, and BDD acceptance criteria to prevent development rework.

    The skill is designed to work with most major LLMs that support Markdown and Mermaid diagrams; simply import the skill into your preferred AI agent platform to begin.

    You receive the full standardized PRD generator logic, the automated quality auditing module, and templates for the Requirements Traceability Matrix (RTM) and ISO-compliant metadata.

    No, the PRD Writer focuses exclusively on systems engineering and requirements logic; it does not generate visual UI designs, wireframes, or low-level database schemas.

    The skill performs a five-dimension weighted self-audit on every document it creates, scoring the output on clarity, verifiability, and completeness based on ISO 25010 characteristics.

    Buyers receive access to all future version updates, including refinements to the ISO 29148 logic and any additions to the non-functional requirement (NFR) benchmarking library.

    New in Business & Operations