Skip to main content
Glama

trw_prd_create

Generate an AARE-F compliant PRD with 12 standard sections, confidence scores, and traceability links from a feature description. Automatically updates catalogue and roadmap.

Instructions

Generate an AARE-F compliant PRD from a feature description.

Use when:

  • You have a feature request or requirements and need a structured PRD.

  • Before writing code for a P0/P1/P2 feature or risky behavioral change.

  • You want auto-incremented PRD ID, YAML frontmatter, and catalogue sync.

Produces 12 standard sections, confidence scores, and traceability links. Updates INDEX.md/ROADMAP.md when index_auto_sync_on_status_change is on.

Input:

  • input_text: feature request or description (becomes Problem Statement + Background).

  • category: one of CORE, QUAL, INFRA, LOCAL, EXPLR, RESEARCH, FIX (plus any values added to .trw/config.yaml::extra_prd_categories).

  • priority: P0, P1, P2, or P3 — drives base confidence scores.

  • title: auto-generated from input_text when empty.

  • sequence: auto-increments from existing catalogue when default (1).

  • risk_level: optional critical|high|medium|low — scales validation strictness.

Output: PrdCreateResultDict with fields {prd_id: str, title: str, category: str, priority: str, output_path: str, content: str, sections_generated: int, index_synced: bool}.

Example: trw_prd_create(input_text="Add rate limiting to public API", category="CORE", priority="P1") → {"prd_id": "PRD-CORE-001", "output_path": "docs/requirements-aare-f/prds/PRD-CORE-001.md", "sections_generated": 12, "index_synced": true, ...}

See Also: trw_prd_validate

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleNo
categoryNoCORE
priorityNoP1
sequenceNo
input_textYes
risk_levelNo
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations exist, so the description fully carries the burden. It details outputs (12 sections, confidence scores, traceability), auto-update behavior for INDEX.md/ROADMAP.md, auto-generation of title and sequence, and scaling of validation based on risk_level. Does not explicitly mention whether it overwrites existing files or is purely append, but the creation context implies non-destructive behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured with clear sections: purpose, usage conditions, parameter list with bullets, output description, example, and cross-reference. No extraneous sentences; each part serves a distinct role.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite no annotations and no output schema, the description covers all needed context: inputs, processing behavior, output structure (with fields enumerated), side effects (catalogue sync), and an illustrative example. It is fully self-contained for an agent to understand and invoke correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 0% description coverage, but the tool description provides detailed semantic context for all 6 parameters including default behavior, valid values, and impact on output. For example, 'category: one of CORE, QUAL, INFRA...' and 'title: auto-generated from input_text when empty'—adds meaning far beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it generates an AARE-F compliant PRD from a feature description. It lists specific use cases and distinguishes itself from sibling tool 'trw_prd_validate' via the 'See Also' section, providing a specific verb+resource+scope.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit 'Use when' bullets outline appropriate contexts: having a feature request, before writing code for P0/P1/P2 features, and need for structured PRD with auto-increment IDs. Also implies when not to use via reference to 'trw_prd_validate'.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/wallter/trw-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server