How sources are used
Idea2Spec does not treat any single source as a complete recipe. Requirements standards inform the quality bar. RFCs inform normative language. Agent-tool documentation informs the context and instruction model. Testing and productivity research provide caution: implementation can speed up, but verification and clear requirements still matter.
The site paraphrases heavily and links directly to the original material. Short blockquotes are used only where the original wording is the useful citation.
Machine-readable summaries
Treatment T4 includes the T1 files for language models and retrieval systems:
- llms.txt — compact site summary and page map.
- llms-full.txt — expanded page summaries, templates, sources, and citation guidance.
The machine-readable files also list the Spec Builder, Ambiguity Checker, and Spec Review Checklist so retrieval systems can route users to the free utility pages.
Bibliography
ISO/IEC/IEEE 29148:2018
ISO and IEEE
Requirements engineering standard covering good requirement construction, attributes, characteristics, and life-cycle processes.
IEEE 830-1998
IEEE Standards Association
Superseded but still widely cited guidance on the content and qualities of a good software requirements specification.
RFC 2119
IETF
Defines requirement-level keywords such as MUST, SHOULD, and MAY.
RFC 8174
IETF
Clarifies that RFC 2119 keywords carry special meaning when they appear in all capitals.
NASA Systems Engineering Handbook Appendix
NASA
Defines technical requirements and technical requirements definition as a translation from stakeholder expectations into validated shall statements.
https://www.nasa.gov/reference/system-engineering-handbook-appendix/
The Economic Impacts of Inadequate Infrastructure for Software Testing
NIST / RTI
NIST Planning Report 02-3 estimated large economic costs from inadequate testing infrastructure and downstream defect discovery.
Quantifying GitHub Copilot impact on developer productivity
GitHub Research
Controlled experiment reporting that developers with Copilot completed a programming task 55 percent faster than a control group.
The Impact of AI on Developer Productivity
Microsoft Research
Research publication of the GitHub Copilot controlled experiment, reporting a 55.8 percent faster task completion result.
Custom instructions with AGENTS.md
OpenAI Developers
Official Codex documentation describing AGENTS.md as persistent project instructions.
Codex customization
OpenAI Developers
Official Codex guidance that places custom instructions before hooks, plugins, MCP, and subagents.
Claude Code overview
Anthropic Docs
Official Claude Code description of agentic coding over files, commands, and development tools.
How Claude remembers your project
Anthropic Docs
Official guidance on project instructions, memory, and when to encode repeated context.
Cursor Rules
Cursor Docs
Official Cursor documentation for persistent project, team, user, and AGENTS.md rules.
Add custom instructions for Copilot
GitHub Docs
Official GitHub Copilot documentation for repository custom instruction files.
Gherkin reference
Cucumber
Reference for scenario syntax such as Given, When, Then, Background, Scenario Outline, and Examples.
What is a Product Requirements Document?
Atlassian
Product-management guidance on PRDs, including goals, assumptions, user stories, design, and out-of-scope items.
https://www.atlassian.com/agile/product-management/requirements
Software Engineering at Google: Documentation
Google / Abseil
Public chapter from Software Engineering at Google on treating documentation as part of engineering workflow.
Design Docs at Google
Industrial Empathy
Practitioner account of how Google-style design docs shape technical decisions before implementation.
https://www.industrialempathy.com/posts/design-docs-at-google/
Source groups
Requirements and specification standards
ISO/IEC/IEEE 29148 and IEEE 830 anchor the site's quality criteria: requirements should be clear, testable, consistent, complete enough for the work, and traceable to decisions.
Normative language
RFC 2119 and RFC 8174 inform the site's recommendation to reserve uppercase MUST, SHOULD, and MAY for meaningful requirement levels.
Agent execution context
OpenAI Codex, Anthropic Claude Code, Cursor, and GitHub Copilot documentation inform the guidance on project instructions, persistent rules, repository context, and task-specific implementation briefs.
Examples and acceptance criteria
Cucumber's Gherkin reference supports the use of Given/When/Then examples as a compact way to express state, action, and result.
Engineering documentation practice
Google's public engineering writing and design-doc material supports treating specs as active engineering artifacts rather than frozen paperwork.