create-tech-spec

create-tech-spec is a cursor rule for Cursor from rweisssieker-xp/GBL-CREO-WINDCHILL-MCP. It costs 270 tokens per session, scanned A, original, MIT.

A conversational workflow for investigating a codebase and producing an implementation-ready technical specification. A technical specification describes what should be built and how it should work.

In plain words
What is it for?
It helps gather requirements, investigate related code, resolve design details, and write a specification that developers can implement.
Why use it?
It turns an unclear development request into a documented plan by asking questions and examining the existing code.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit It helps gather requirements, investigate related code, resolve design details, and write a specification that developers can implement.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/rweisssieker-xp/gbl-creo-windchill-mcp/create-tech-spec
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo
git clone --depth 1 https://github.com/rweisssieker-xp/GBL-CREO-WINDCHILL-MCP

Made for: Cursor.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for create-tech-spec

README.md
[![agentmods](https://agentmods.dev/badge/rules/rweisssieker-xp/gbl-creo-windchill-mcp/create-tech-spec/github.svg)](https://agentmods.dev/rules/rweisssieker-xp/gbl-creo-windchill-mcp/create-tech-spec)
Your own site
<a href="https://agentmods.dev/rules/rweisssieker-xp/gbl-creo-windchill-mcp/create-tech-spec"><img src="https://agentmods.dev/badge/rules/rweisssieker-xp/gbl-creo-windchill-mcp/create-tech-spec/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for create-tech-spec

Your own site · 80×15
<a href="https://agentmods.dev/rules/rweisssieker-xp/gbl-creo-windchill-mcp/create-tech-spec"><img src="https://agentmods.dev/badge/rules/rweisssieker-xp/gbl-creo-windchill-mcp/create-tech-spec.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 270 This file is loaded in full into every session.
When invoked 270 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00270 $0.00270
Opus 5 $0.00135 $0.00135
Sonnet 5 $0.00054 $0.00054
Haiku 4.5 $0.00027 $0.00027

Measured 10d ago against content hash d6d4c2055b11, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

create-tech-spec scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.cursor/rules/bmad/bmm/workflows/create-tech-spec.mdc · 31 lines

What it actually says

Quick-Flow: Create Tech-Spec

name: create-tech-spec description: "Conversational spec engineering - ask questions, investigate code, produce implementation-ready tech-spec." author: "BMad"

Config

config_source: "{project-root}/.bmad/bmm/config.yaml" output_folder: "{config_source}:output_folder" sprint_artifacts: "{config_source}:sprint_artifacts" user_name: "{config_source}:user_name" communication_language: "{config_source}:communication_language" document_output_language: "{config_source}:document_output_language" user_skill_level: "{config_source}:user_skill_level" date: system-generated

Workflow components

installed_path: "{project-root}/.bmad/bmm/workflows/bmad-quick-flow/create-tech-spec" instructions: "{installed_path}/instructions.md"

quick_dev_workflow: "{project-root}/.bmad/bmm/workflows/bmad-quick-flow/quick-dev/workflow.yaml" party_mode_exec: "{project-root}/.bmad/core/workflows/party-mode/workflow.md" advanced_elicitation: "{project-root}/.bmad/core/tasks/advanced-elicitation.xml"

standalone: true

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 10d ago First seen · 31 lines · 270 tokens per session scan A d6d4c2055b11

Subscribe to this mod's changes

create-tech-spec is a cursor rule published in the GitHub repository rweisssieker-xp/GBL-CREO-WINDCHILL-MCP (4 stars, last pushed 9mo ago), licensed MIT. It adds 270 tokens to every session, about $0.0014 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.