- Home
- Skills
- Prompt & Skill Engineering
- Vague Request to Clear Acceptance Criteria
Works with the AI Agents you already use
Vague Request to Clear Acceptance Criteria
Use when a request is long, vague or keeps changing. Gives every requirement an ID and a checkable acceptance criterion, keeps deadlines, counts and do-not-touch limits, and lists the open decisions.
$5
Vague Request to Clear Acceptance Criteria
Example session with this skill installed
I need to add Stripe to our Node app. It should handle subscriptions, send an email on failure, and maybe use their new checkout UI. Needs to be done by Friday.
- Read your context and instructions
- Compiled the vague request to
I have analyzed the request and mapped the intent to an observable acceptance specification.
Intent to Acceptance Specification
Goal: A developer can process recurring payments and handle failure events via Stripe integration in the Node.js environment, delivering the implementation to the feature/payments branch.
| Req # | Status | Artifact | Acceptance Observation |
|---|---|---|---|
| 1 | Included | StripeSubscriptionService | Successful invoice.created event triggers active status in DB. |
| 2 | Included | FailureNotificationWorker | SMTP log shows outgoing mail triggered by invoice.payment_failed. |
| 3 | Pending | Checkout UI Selection | User selects between Custom Flow or Stripe Checkout (Option B). |
| 4 | Included | Deployment Config | main.yml CI pass and merge to branch by Friday 17:00 UTC. |
Prerequisites:
- Stripe Secret Key (Authorization: PENDING)
- Existing Node.js User Model (Authorization: READ-ONLY)
- SMTP Server Credentials (Authorization: PENDING)
Unknowns and Defaults:
- Default: Using
Stripe-Signatureheader verification for webhooks (Reason: Security best practice).
Ambiguity: "Maybe use their new checkout UI". (Direction: If Stripe Checkout is used, internal frontend work decreases but customization is limited).
Next Step:
Confirm if Stripe Checkout is preferred over a custom elements integration.
Completion Signal: User selects one UI implementation path.
Next steps
- Provide the Stripe Secret Key and SMTP credentials.
- Confirm the choice between Stripe Checkout and a custom UI integration.
Connects securely to your tools. The creator never sees your data.
About this skill
Vague user requests and mixed requirements lead to scope creep and wasted engineering hours. This skill forces clarity by converting messy intent into a structured, per-item acceptance specification before a single line of code is written.
What it does
- Requirement Mapping links every original request item to a specific artifact and observable result.
- Dependency Tracking identifies prerequisites and their current authorization state to prevent blockers.
- Conflict Resolution prioritizes explicit prohibitions over implementation preferences to maintain boundaries.
- Decision Management provides reversible defaults for low-impact details while flagging directional ambiguities for user input.
- Outcome Validation defines exactly what must be observed to prove a requirement is satisfied.
How it works
- Analyze the incoming request to number and categorize every condition, unit, and deadline.
- Filter outcomes from processes and preferences, identifying what is strictly required versus optional.
- Draft the specification including a requirement map, prerequisites, and handled unknowns.
- Submit the structured spec as a standalone artifact for confirmation before implementation begins.
Frameworks & tools
This skill is framework-agnostic and works with any development environment, project management tool, or ticketing system where technical requirements are defined.
Why this beats prompting it yourself
Generic prompts often skip the "observable" part of acceptance criteria or hallucinate user decisions when faced with ambiguity. This skill enforces a strict logic for handling unknowns and ensures that no requirement vanishes during the transition from intent to specification.
Use cases
- Refining a loose feature request from a non-technical stakeholder.
- Auditing a messy Jira ticket before starting a sprint task.
- Defining success criteria for complex refactoring jobs.
- Scoping external API integrations where authorization and dependencies are unclear.
Known limitations
This skill produces specifications only and will not perform the implementation. It requires an initial request or context to function.
Produces specifications only; does not perform implementation. Requires an initial request or context to function.
How to use
- 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
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 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 7 days ago
Permissions
No special permissions declared or detected