Generates traceable EARS requirements and a three-document spec from user discovery sessions.
npx skills add https://github.com/scottopell/dotfiles --skill spears
Please help me install this Agent Skill. Skill: spears Source: https://github.com/scottopell/dotfiles/tree/main/home-dir-configs/claude/skills/spears Command: npx skills add https://github.com/scottopell/dotfiles --skill spears
spEARS (Simple Project with EARS) provides Socratic discovery of user needs, EARS-formatted specification writing, implementation tracking, and spec validation -- all built on a strict three-document pattern (requirements.md, design.md, executive.md).
Start a discovery session to surface user needs and generate the three-document spec with traceable EARS requirements.
High-intent search queries and answers about installing and using this skill.
EARS-formatted specification writing structures traceable requirements across a three-document pattern: requirements.md for needs, design.md for self-contained design traces, and executive.md for structured status across the spec lifecycle.
The three-document pattern for spec writing divides project governance into requirements.md, design.md, and executive.md, ensuring self-contained design traces and structured executive status across the entire spec lifecycle.
Start a Socratic discovery session to define user needs by prompting the workflow to surface real problems worth solving, which then generates the foundational requirements needed for the three-document spec structure.
Yes, this spec writing approach supports implementation tracking and validation by applying governance checks that ensure design traces stay self-contained and requirements remain aligned to user outcomes throughout the lifecycle.
The best way to maintain traceability between design and requirements is using a strict three-document pattern with EARS-formatted requirements, enforcing governance checks that keep design traces self-contained and aligned to validated user outcomes.
Avoid using a strict three-document spec lifecycle for rapid prototyping or informal brainstorming where heavy governance, EARS-formatted requirements, and structured executive status tracking would create unnecessary process overhead.
ben-mad-jlpExplore codebases, documentation, and commit history to gather project context.
daddiaImplement code from an approved design.md and backlog.md with tests.
jinwoonghongOrchestrate a full software development lifecycle pipeline from planning to deployment.
dundasGenerate user stories with acceptance criteria in Markdown format.
