Create a formatted feature
create_formatted_featureCreates a Targetprocess Feature with a structured, template-driven description and required NFR rows so cross-cutting constraints, risks, and open questions stay testable and auditable.
Instructions
Create a new Feature in Targetprocess with a structured, template-driven description (feature-level TDRE), assembled from discrete sections and stored as HTML. Features sit above user stories — this template isn't about writing Gherkin for individual behaviors (that belongs on child stories); it's about tracking cross-cutting constraints, risks, and open questions to a testable/decided state before they get lost across many separate stories. Fill in each field to this quality bar: 1) Header — "businessBackground" is a 1-2 sentence value statement: who benefits and why; 2) Definitions — cross-cutting terms used across multiple child stories, so they aren't redefined at every story level; if none apply, OMIT "definitions" entirely (do not send an empty section); 3) Scope & Boundaries — what this feature explicitly includes/excludes, to stop child stories drifting into adjacent features; omit if genuinely trivial; 4) Non-Functional Requirements ("nonFunctionalRequirements") — this is the core of the template and doubles as ISO 27001:2022 audit evidence that NFRs (including information security, per Annex A Control 5.8) are considered at design time, not bolted on after. EVERY feature MUST include these four fixed rows, worded exactly as below (do not reword the questions — consistency in the questions is what makes them auditable), each answered SPECIFICALLY for this feature in "storyOrOwner" — a real, checkable answer (e.g. which systems/data/roles are involved), never a generic "considered" placeholder: - area "System performance" / requirement "What does this feature add or change in terms of load, queries, polling, rendering etc., and what's the expected impact, if any?"; - area "Information security (ISO 27001:2022 Annex A 5.8)" / requirement "What personal or sensitive data does this feature touch, and what protects its privacy, confidentiality, integrity and availability?"; - area "Quality control" / requirement "How will this feature's behaviour and failures be measured or tested, and what happens when it fails?"; - area "Service logging" / requirement "What events or states should be logged so product support can diagnose an issue without reproducing it manually?"; For each row, set status to "Covered" (storyOrOwner holds the specific answer, or the child story/scenario that proves it), "Gap" (no answer/story yet — storyOrOwner names who should follow up), or "Decision needed" (genuinely open, not answerable yet). If any of the four is unclear, follow-up owner in rather than guessing — he's the named escalation contact, not a mandatory sign-off gate. Additional NFR categories beyond these four (Compliance, Billing, Operational, etc.) can still be added as extra rows when relevant, using the same Covered/Gap/Decision-needed treatment; 5) Cross-Cutting Scenarios — ONLY for behavior spanning multiple child stories that wouldn't naturally sit in any one of them (e.g. tenant isolation across all stories); do not duplicate per-story Gherkin here; omit if none apply; 6) Child Stories ("childStories") — pull this from "get_feature_user_stories" / "get_not_covered_user_stories_in_feature" rather than retyping it; keep it as a live pointer, not a duplicate spec; normally empty when first creating the feature; 7) Open Questions / Risks ("openQuestions") — anything raised at feature conception that hasn't been resolved into either a Covered NFR row or a child story; this is the section most likely to get silently dropped — treat it as the running "not done yet" list until each line is promoted to a Covered NFR row; 8) References — mockup/spec links here, not inline in prose; 9) Notes — anything else that helps understand context but doesn't fit other sections; CRITICAL WORKFLOW: Before calling this tool, you MUST follow these steps: 1) IF the user specified an epic by name (not ID), resolve the epic ID first; 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 this feature already has child stories, call "get_feature_user_stories" and "get_not_covered_user_stories_in_feature" to build "childStories" instead of guessing coverage;
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>",
"nonFunctionalRequirements": "<nonFunctionalRequirements>"
},
"name": "create_formatted_feature"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| notes | No | Anything else that helps understand context but does not fit other sections | |
| scope | No | Scope & Boundaries. Omit if genuinely trivial | |
| title | Yes | Feature title | |
| epicId | No | Optional Epic ID to link this feature to (e.g. 145636) | |
| header | Yes | Feature header | |
| teamId | No | Optional Team ID — defaults to TP_TEAM_ID from config | |
| projectId | No | Optional Project ID — defaults to TP_PROJECT_ID from config | |
| releaseId | No | Optional Release ID to link this feature to (e.g. 145200) | |
| references | No | Links to specs/mockups (not inline in prose) | |
| definitions | No | Cross-cutting terms used across multiple child stories, avoiding re-defining the same term at every story level. Omit entirely if none apply | |
| childStories | No | Pull this from "get_feature_user_stories" / "get_not_covered_user_stories_in_feature" rather than retyping it — a live pointer, not a duplicate spec. Normally empty when first creating the feature | |
| openQuestions | No | Anything raised at feature conception not yet resolved into a Covered NFR row or a child story — the running "not done yet" list | |
| crossCuttingScenarios | No | Only for behavior spanning multiple child stories that would not naturally sit in any single one of them. Do not duplicate per-story Gherkin here; omit if none apply | |
| nonFunctionalRequirements | Yes | Every NFR category converted from prose into a testable/decided row — the core of this template. MUST include the four fixed rows required for ISO 27001:2022 audit evidence: "System performance", "Information security (ISO 27001:2022 Annex A 5.8)", "Quality control", and "Service logging" — worded exactly, each answered specifically for this feature (escalate unclear items to story owner). Additional categories may be added beyond these four. Do not leave requirements as untested prose |