What is reqforge-dev-build?

A development workflow guide for implementing software from a development plan, one task at a time.

Use it to build planned features with TDD—writing a failing test before the code—then review and record each completed task.

It structures coding, testing, review, documentation, compilation checks, and commits so work is easier to verify.

reqforge-dev-build — Cursor rule by zxpmail

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.

agentmods

npx agentmods add rules/zxpmail/reqforge/reqforge-dev-build

Clone the repo

git clone --depth 1 https://github.com/zxpmail/ReqForge

Made for: Cursor.

Per session 444 This file is loaded in full into every session.

When invoked 444 The same file — it is already loaded in full.

Security scan A 0 findings. Scan, not verified.

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.

Model	Per session	Once invoked
Fable 5	$0.00444	$0.00444
Opus 5	$0.00222	$0.00222
Sonnet 5	$0.00089	$0.00089
Haiku 4.5	$0.00044	$0.00044

Measured yesterday against content hash 59d915cf5412, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

reqforge-dev-build 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 yesterday.

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.

adapters/cursor/.cursor/rules/reqforge-dev-build.mdc · 39 lines

What it actually says

Dev Builder

Full skill definition: .cursor/rules/skills/dev-builder/SKILL.md

Before Each Phase: Plan + TaskList

Read Phase delivery checklist and key files from DEV-PLAN.md
Explore existing code structure
Plan implementation steps
Use TaskCreate to break into specific Tasks
No code without a Plan — this is non-negotiable

Per-Task Loop

Before coding: Load reference docs — read task description from DEV-PLAN, feature description from Product-Spec.md, design direction from Design-Brief.md
TDD: Write test first (RED) → minimal code to pass (GREEN) → refactor (REFACTOR)
After coding: Cross-reference against Spec, verify design values, check feature completeness
Code review: Parallel specialized agents (or quick check for simple changes)
Memory update: Append to task-history.md (mandatory). If decision made → decisions-log.md. If architecture changed → project-memory.md.
Commit: Atomic commit after each Task. Must compile (tsc --noEmit zero errors) before commit.

Phase Completion: Four-Step Verification

Code Review — check delivery checklist item by item
Test Completeness — all features implemented
Compile Check — tsc --noEmit zero errors
Functional Test — start dev server, verify no errors

If any step fails → dispatch feedback-observer → fix → restart from Step 1.

One Phase Per Invocation

After Phase verification passes → stop. Do not start the next Phase. User must invoke /dev-builder again.

Design Reference

If design tool MCP is available: read exact values before each Task, implement component by component, verify after implementation. Design draft takes precedence over Design-Brief.md.

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.

yesterday First seen · 39 lines · 444 tokens per session scan A 59d915cf5412

Subscribe to this mod's changes

reqforge-dev-build is a cursor rule published in the GitHub repository zxpmail/ReqForge (18 stars, last pushed 11d ago), licensed MIT. It adds 444 tokens to every session, about $0.0022 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-30.

Code review Data and AI Testing agent-harness ai-agents ai-coding claude-code cursor developer-tools

language-agnostic-patterns

Language-agnostic programming patterns: SOLID, design patterns, clean code, and architecture. Load when refactoring, designing abstractions, or reviewing structure — not for everyday syntax.

madebyaris/advance-minimax-m3-cursor-rules · 37 tokens

cursor-tools-mastery

Cursor 3.7 runtime guide: choose the right tool, canvases, Design Mode, /worktree, /best-of-n, Await, and parallel execution where safe.

madebyaris/advance-minimax-m3-cursor-rules · 36 tokens

fable5-reasoning

Fable 5 reasoning protocols: task interpretation, risk-first decomposition, approach selection, interleaved thinking, hypothesis ledgers, premortems, calibration, and the stuck-strategy ladder. Load for complex, ambiguous, or long-horizon tasks, for debugging strategy, or whenever progress stalls.

madebyaris/advance-minimax-m3-cursor-rules · 60 tokens

reqforge-dev-build