- Home
- Skills
- Business & Operations
- solutioning analyst
solutioning analyst
Generates implementation-ready BRDs, HLDs, ERDs, and API contracts from raw requirements and UI designs.
$1
Works with the AI Agents you already use
solutioning analyst
Example session with this skill installed
Create an IFA for a new 'Order Creation' API based on the requirement that users must be authenticated and the system should return a standard success envelope with an orderId.
- Read your context and instructions
- Compiled the solutioning analyst
I have generated the IFA for the Order Creation API. It includes the required sequence diagram, SLA targets, and the standard status envelope for responses.
IFA Order Creation API
Design
The Order Creation API allows authenticated users to submit new orders. The system validates the session, processes the order in the ord-svc domain, and persists data to the order database.
Sequence Diagram
sequenceDiagram
participant User
participant Gateway
participant OrderService
participant DB
User->>Gateway: POST /v1/orders
Gateway->>OrderService: Forward Request
OrderService->>DB: Save Order
DB-->>OrderService: Success
OrderService-->>Gateway: 200 OK (Status Envelope)
Gateway-->>User: 200 OK
Performance / SLA Targets
| Success Rate | VUser | CPU / Memory | Response Time |
|---|---|---|---|
| 99.9% | TBD | TBD | < 200ms |
General Information
- Endpoint:
POST /v1/orders - Exposure: Internal Only
- Version: v1.0
Business Rules
- User must have an active session token.
- Request must contain at least one item.
Response Body
{
"status": {
"code": "ORDS00000",
"message": "Order created successfully"
},
"data": {
"orderId": "ORD-12345"
}
}
Next steps
- Review the TBD values in the SLA Targets table.
- Verify the
orderIdformat with the database team. - Confirm if this endpoint requires VA/Pentest based on exposure rules.
Connects securely to your tools. The creator never sees your data.
About this skill
Stop wasting time on inconsistent technical specifications. Manual documentation often leads to logic gaps, missing SLA targets, and broken API contracts that slow down development teams. This skill transforms Figma files, raw requirements, and meeting notes into implementation-ready technical documents that follow the System Analyst Playbook v1.6.
What it does
- Standardized API contracts generates IFA (Interface Agreement) documents with sequence diagrams, SLA targets, and nested status envelopes.
- Structural data modeling produces ERD deliverables including entity attributes, constraints, indexes, and relationship rules.
- High-level architecture builds HLD documents with deployment topologies, integration flows, and linked architecture SVGs.
- Business requirement mapping crafts BRDs with traceable IDs, stakeholder scope, and delivery sequences.
- Glossary management maintains cross-document terminology to ensure naming consistency across large systems.
How it works
- Provide a source such as a Figma link, screenshot, BRS, or feature description.
- The agent classifies impacts as New, Enhancement, or Existing while separating facts from assumptions.
- It generates the requested document (IFA, ERD, HLD, BRD, or Glossary) using precise Markdown templates.
- It validates the output for Playbook compliance, ensuring required sections like SLA tables and Mermaid diagrams are present.
Frameworks & tools
Uses Mermaid.js for sequence and flow diagrams. Supports specific database engines and application stacks based on source evidence. Outputs standard Markdown and SVG architecture diagrams.
Why this beats prompting it yourself
Writing these documents requires strict adherence to template structures and complex business logic validation that generic prompts miss. This skill enforces specific error code categories, mandatory SLA columns, and nested JSON response envelopes out of the box.
Use cases
- Drafting detailed API contracts for frontend-backend handoff.
- Mapping database schema changes for a legacy-to-modern transformation.
- Generating high-level architecture diagrams for stakeholder approval.
- Synchronizing business requirements with technical solutioning documents.
Known limitations
Does not support MongoDB unless explicitly specified in sources. Default language for validation messages is Bahasa Indonesia. Architecture SVGs require a linked relative path configuration.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Business & Operations.
Default language is Bahasa Indonesia. Requires specific reference templates to be present in the environment. Does not invent SLA or schema values if missing from source.
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 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 15 days ago