Create a formatted user story
create_formatted_user_storyCreates structured Targetprocess user stories from As a/I want/so that headers, Gherkin scenarios, edge cases, and traceable acceptance criteria as template-driven HTML.
Instructions
Create a new user story in Targetprocess with a structured, template-driven description, assembled from discrete sections and stored as HTML. Fill in each field to this quality bar: 1) Header — "asA" and "iWant" must be filled in, and "soThat" MUST be a real business outcome, not a restatement of "iWant"; 2) Definitions — check for jargon, feature flags, module names, and acronyms; if none apply, OMIT the "definitions" field entirely (do not send an empty section); 3) Scenarios (write these BEFORE acceptanceCriteria) — at least one Gherkin scenario per distinct behavior; each scenario has exactly ONE "Then" outcome (split it into two scenarios if it needs two); avoid vague verbs like "system validates input" — spell out exactly what "validates" means in the "Then" step; 4) Examples Table — if any behavior is described as "supports various formats/roles/states", convert it into a Scenario Outline (one of the "scenarios" entries) plus a matching "examplesTable" with real values; if no parameterized behavior exists, OMIT "examplesTable"; 5) Edge Cases — MANDATORY (include at least one error-state scenario and one boundary-condition scenario in "edgeCases") if the story touches validation/input handling, permissions/roles, or external data/integrations; otherwise OMIT "edgeCases"; 6) Acceptance Criteria — every bullet MUST be traceable to a specific scenario or edge case above; if a bullet isn't backed by a scenario, it isn't a criterion yet — put it in "notes" as a flagged gap instead; 7) References — put mockup/spec links here, not inline in prose; 8) Notes — capture open questions or known constraints here; don't let them hide inside acceptanceCriteria; CRITICAL WORKFLOW: Before calling this tool, you MUST follow these steps: 1) IF the user specified a feature by name (not ID), call "get_feature_user_stories" or "search_tp_cards" to resolve the feature ID; 2) IF the user specified a release by name (not ID), call "get_current_releases" to resolve the release ID; 3) IF the user specified a team by name (not ID), call "get_teams" to find the matching team and use its ID as teamId; 4) IF the user specified a project by name (not ID), call "get_projects" to find the matching project and use its ID as projectId; 5) IF the user specified a sprint/iteration by name, call "get_team_iterations" to find the matching iteration and use its ID as teamIterationId;
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"title": "<title>",
"header": "<header>",
"scenarios": "<scenarios>",
"acceptanceCriteria": "<acceptanceCriteria>"
},
"name": "create_formatted_user_story"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| tags | No | Optional comma-separated tags to apply, e.g. "regression, mobile" | |
| notes | No | Open questions or known constraints that do not fit other sections — do not let these hide inside acceptanceCriteria | |
| title | Yes | User story title | |
| header | Yes | Story header following the As a / I want / so that format | |
| teamId | No | Optional Team ID — defaults to TP_TEAM_ID from config | |
| edgeCases | No | Explicit edge case or boundary condition scenarios. MANDATORY — at least one error-state and one boundary-condition scenario — if the story touches validation/input handling, permissions/roles, or external data/integrations; omit otherwise | |
| featureId | No | Optional Feature ID to link this user story to (e.g. 145636) | |
| projectId | No | Optional Project ID — defaults to TP_PROJECT_ID from config | |
| releaseId | No | Optional Release ID to link this user story to (e.g. 145200) | |
| scenarios | Yes | Gherkin scenario blocks, one per distinct behavior. Write these before acceptanceCriteria | |
| references | No | Links to Axure mockups or other external references (not inline in prose) | |
| definitions | No | Jargon, feature flags, module names, or acronyms that need defining. Omit entirely if none apply — do not send an empty section | |
| examplesTable | No | Examples: table with real values backing a Scenario Outline for parameterized/matrix behavior (e.g. "supports various formats/roles/states"). Omit if no parameterized behavior exists | |
| teamIterationId | No | Optional Team Iteration (sprint) ID — resolve it via "get_team_iterations" first | |
| acceptanceCriteria | Yes | Bullet checklist items for quick review sign-off — each string is one criterion. Every bullet MUST be traceable to a specific scenario or edge case above |