brycewang-stanford/sdd
skills/09-meleantonio-awesome-econ-ai-stuff/_skills/engineering/sdd/SKILL.md
Implements the Spec-Driven Development lifecycle (Intent, Requirements, Design, Tasks, Build) for structured feature development. Use when the user wants to scaffold a new feature spec, generate EARS requirements, create a technical design, break work into tasks, or check spec status. Trigger on keywords: sdd, spec-driven, ears requirements, feature spec.
$ install --global
skillsauthnpx skillsauth add brycewang-stanford/Awesome-Agent-Skills-for-Empirical-Research sddInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 15, 2026, 10:42 PM29.1s7 files scanned
SKILL.md
- name:
- sdd
- description:
- >
- Trigger on keywords:
- sdd, spec-driven, ears requirements, feature spec.
- workflow_stage:
- engineering
- author:
- Awesome Econ AI Community
- version:
- 1.0.0
Spec-Driven Development (SDD)
Core Philosophy
- Clarity before Code: Never generate code until requirements and design are approved.
- Iterative Refinement: Loop through Req → Design → Tasks until solid.
- Code via Docs: The truth is in the markdown files, not the chat.
Commands
Execute in the project root (where spec/ and steering/ live).
init
Scaffold the SDD folder structure and template files.
- If
spec/already exists, skip or ask before overwriting. - Create
spec/andsteering/. - Create
spec/intent.md(blank or minimal placeholder). - Copy templates from this skill’s
templates/directory (in the same folder asSKILL.md, or from your install path under~/.cursor/skills/sdd/after copying the skill there) into the project:templates/spec/requirements.md→spec/requirements.mdtemplates/spec/design.md→spec/design.mdtemplates/spec/tasks.md→spec/tasks.mdtemplates/steering/coding-standards.md→steering/coding-standards.md
reqs
Generate EARS requirements from intent.
- Read
spec/intent.mdandsteering/*.md. - Convert the intent into EARS requirements (see EARS Quick Reference below). Add a Properties (invariants) section.
- Write to
spec/requirements.md. - Ask for user approval before proceeding.
design
Generate technical design from requirements.
- Read
spec/requirements.mdandsteering/*.md. - Create a technical design: architecture, data models, component interfaces, error handling, security. Apply the Design Checklist below.
- Write to
spec/design.md. - Ask for user approval before proceeding.
tasks
Generate implementation tasks from design.
- Read
spec/design.mdandspec/requirements.md. - Create a sequential task list: max two levels (Task > Subtask). Link each task to requirement IDs (e.g.
REQ-001). Follow Task Rules below. - Write to
spec/tasks.md. - Ask for user approval before proceeding.
status
Report current state of the spec.
- List files in
spec/(and optionallysteering/). - If
spec/tasks.mdexists, count unchecked[ ]vs checked[x]and summarize.
EARS Quick Reference
- Ubiquitous:
<system> shall <response> - Event-Driven:
WHEN <trigger> [precondition] the <system> shall <response> - Unwanted:
IF <unwanted condition> THEN the <system> shall <response> - State-Driven:
WHILE <system state>, the <system> shall <response> - Optional:
WHERE <feature is included>, the <system> shall <response>
Use IDs like [REQ-001]; add a Properties (Invariants) section for universal correctness statements.
Design Checklist
- Edit ruthlessly (remove over-engineering).
- Check for circular dependencies; fix via interface extraction, layering, or events.
- Ensure alignment with steering documents.
Task Rules
- Two-level hierarchy maximum (Task > Subtask).
- Sequential order (each task builds on previous).
- Traceability: each task or subtask links back to requirement IDs (e.g. Traceability: Implements
REQ-001).
Additional Resources
- For full framework detail (workflow, refinement, iteration triggers), see reference.md.
Related Skills
brycewang-stanford/literature-review-tools
tools
VerifiedTrustedCommunity
Recommend AND run open-source AI tools, agents, Claude Code / Codex skills, and MCP servers for any stage of a literature review — searching, reading, extracting, synthesizing, screening, citation-checking, and paper writing. Use when the user asks "what tool should I use to..." OR "install/run/use <tool> to ..." for research/lit-review work: automating a survey or related-work section, PDF→Markdown extraction for LLMs (MinerU/marker/docling), PRISMA / systematic review (ASReview), citation-backed Q&A over PDFs (PaperQA2), wiring papers into Claude/Cursor via MCP (arxiv/paper-search/zotero servers), or chatting with a Zotero library. Ships a launcher (scripts/litrun.py) that installs each tool in an isolated venv and runs it. Curated catalog of 70+ vetted projects. 支持中英文（用于「文献综述工具选型」与「一键安装/运行」）。
3,109SKILL.mdUpdated Jul 28, 2026
brycewang-stanford/auto-empirical-research-skills
development
VerifiedTrustedCommunity
Route empirical-research requests through the Auto-Empirical Research Skills catalog when this whole repository is installed as one skill in Codex, CodeBuddy, Claude Code, or another IDE. Use to choose and load the right vendored AERS skill for causal inference, econometrics, replication, data acquisition, manuscript writing, peer review and referee responses, citation checking, de-AIGC editing, or full empirical-paper workflows without reading the entire repository at once.
3,109SKILL.mdUpdated Jun 27, 2026
brycewang-stanford/aer-preregistration
documentation
VerifiedTrustedCommunity
Use when the project collects primary data or runs a field, lab, or survey experiment, before the intervention begins — write the pre-analysis plan, size the sample from a power calculation, and register with the AEA RCT Registry. Apply after the design is chosen in aer-identification and before any outcome data are seen.
3,021SKILL.mdUpdated Jul 23, 2026
brycewang-stanford/economist-data-skill
tools
VerifiedTrustedCommunity
Guide economists to authoritative data sources with explicit, confirmed data specifications before retrieval; interfaces with Playwright MCP to navigate portals and extract real data, not articles about data.
3,021SKILL.mdUpdated Jul 23, 2026