requirements analysis

    1

    Perform rigorous static testing on requirements to catch ambiguities and missing criteria before implementation.

    $10

    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 CLIDeepSeekDeepSeekMuseMuse+22 more

    requirements analysis

    Example session with this skill installed

    Analyze this user story: As a user, I want the search results to load immediately and show relevant items. AC:

    1. Search works.
    2. Results are displayed.
    • Read your context and instructions
    • Compiled the requirements analysis

    I have completed the requirements analysis for the Search Results user story.

    Requirements Analysis Report

    IDSource quote/locationCategoryIssue or testable criterionSeverityImpactProposed clarification/rewrite
    AC-1"load immediately"UntestableMissing measurable timing and network context.CriticalCannot pass/fail."Results display within 200ms on 4G."
    AC-2"relevant items"Ambiguity"Relevant" is subjective; no sorting/ranking logic defined.MajorWrong data shown.Define ranking by "Newest" or "Keyword Match".
    AC-3"Search works"UndefinedDoes not specify triggers (Enter key, icon click, or type-ahead).MajorImplementation gap."Search triggers after 3 chars or on Enter."
    GAP-1N/AMissingNo zero-results state defined.MinorUX dead end.Add AC for "No results found" message.

    Questions

    • Business rule: What is the maximum number of results to display per page?
    • UI/flow: Should the search filter apply as the user types or only after submission?
    • Data/integration: Which specific database fields are included in the "relevance" calculation?

    Assumptions (unconfirmed)

    • Search is restricted to the primary product catalog only.
    • User is already authenticated before accessing search.

    Readiness: NEEDS CLARIFICATION
    The requirement is blocked by untestable performance targets ("immediately") and undefined relevance logic.

    Next steps

    1. Review the proposed rewrites with the Product Owner to define "relevance."
    2. Define the technical latency threshold (e.g., 200ms or 500ms).
    3. Document the "No Results" behavior.

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

    About this skill

    Vague user stories and incomplete acceptance criteria lead to scope creep and expensive late-stage bug fixes. This skill performs rigorous static testing on your requirements to catch ambiguities before a single line of code is written.

    What it does

    • Ambiguity detection identifies unverifiable terms like "fast" or "appropriate" that prevent clear pass/fail outcomes.
    • Gap analysis uncovers missing boundary conditions, error states, and undefined business rules in your specifications.
    • Traceability mapping builds a direct link from source requirements to testable outcomes across functional and non-functional domains.
    • Criteria refinement generates proposed rewrites for acceptance criteria to ensure they are measurable and actor-oriented.
    • Readiness assessment provides a structured GO/NO-GO disposition based on unresolved blockers and implementation risks.

    How it works

    1. Extraction of actors, goals, triggers, and data flows from your raw text or project files.
    2. Static review against ISO/IEC 25010 quality characteristics to find conflicts or untestable wording.
    3. Question generation where the agent asks prioritized questions categorized by business rules, UI, and integration needs.
    4. Final reporting using a standardized table format that includes impact scores and proposed clarifications.

    Frameworks & tools

    The skill follows ISTQB static testing principles and ISO/IEC 25010 quality standards. It is optimized for use within Claude Code, Cursor, or ChatGPT when analyzing Markdown-based requirements, Jira exports, or PRD documents.

    Why this beats prompting it yourself

    Generic prompts often miss non-functional requirements or silently hallucinate product behavior to fill gaps. This skill enforces a strict evidence-readiness gate, ensuring every suggestion is traceable to your source text rather than an LLM guess.

    Use cases

    • Reviewing a new PBI or User Story before a sprint planning session.
    • Analyzing UI mockups to find missing validation messages and error states.
    • Auditing a change request for impacts on existing system dependencies.
    • Performing a formal peer review on technical specifications or API contracts.

    Known limitations

    Does not replace stakeholder decisions or provide legal compliance guarantees. Requires a writable folder for saving reports if used in a local CLI environment.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Code Quality & Review.

    Requires user confirmation for output folders. Cannot resolve business conflicts without stakeholder input. Does not guarantee compliance with external standards.

    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

    Money-back guarantee

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

    Trust & safety

    Security scan

    Security scan passed 2 days ago

    Permissions

    Read Files
    Write Files
    Listed2 days ago

    What's inside

    Frequently Asked Questions

    The skill identifies 'hidden' defects—such as unverifiable adjectives, missing error states, and logic gaps—that standard prompts often overlook or hallucinate solutions for. By enforcing ISO/IEC 25010 standards, it ensures your requirements are testable and developer-ready before a single line of code is written.

    This skill is optimized for LLMs with file-access capabilities like Claude Code, Cursor, and ChatGPT. It performs best when it can read and write Markdown-based documentation, Jira exports, or PRD files directly within your development environment.

    No complex installation is required; once imported into your agent, you simply provide your raw requirements text or file path. The agent will then guide you through the four-stage process of extraction, static review, question generation, and final reporting.

    You will receive the core skill logic, a library of static testing templates, and a guide on how to integrate the skill into your specific workflow. This includes the standardized table format for final impact reports.

    Yes, it is specifically designed to audit technical specifications, including API contracts and system dependency maps. It identifies missing validation messages, data flow inconsistencies, and integration risks that often cause late-stage bugs.

    Purchasers receive lifetime access to the current version, including any patches or performance optimizations released to align with updates in the underlying AI models (like Claude or GPT-4).

    New in Code Quality & Review