mikeparcewski/wicked-garden-product-requirements-analysis
skills/product/requirements-analysis/SKILL.md
Use when turning a vague idea or stakeholder ask into structured user stories with acceptance criteria and a requirements graph. For complexity >= 3 or compliance projects, defaults to graph mode. NOT for navigating an existing requirements graph (use requirements-navigate) or stakeholder alignment (use product:align).
$ install --global
skillsauthnpx skillsauth add mikeparcewski/wicked-garden wicked-garden-product-requirements-analysisInstall 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: Jul 13, 2026, 8:02 AM137.4s5 files scanned
SKILL.md
- name:
- wicked-garden-product-requirements-analysis
- description:
- |
- NOT for navigating an existing requirements graph (use requirements-navigate) or stakeholder alignment (use product:
- align).
- phase_relevance:
- ["clarify", "design", "review"]
- archetype_relevance:
- ["*"]
Requirements Analysis Skill
Structured requirements elicitation from discovery through documentation.
Default: Graph mode. For complexity >= 3 or compliance projects, produce a
requirements/graph (seerequirements-graphskill) instead of a monolithic document. Use--monolithto force the legacy single-file format. See:requirements-graph/SKILL.mdfor graph layout and schema. See:requirements-navigate/SKILL.mdfor querying and maintaining the graph.
Process
1. Context Gathering
- Read project brief, outcome.md, or requirements
- Identify existing documentation
- Note assumptions and constraints
2. Stakeholder Identification
- Who are the users/personas?
- Who are secondary stakeholders?
- Who has decision authority?
3. Requirements Elicitation
Ask the 5 W's:
- Who: Which users/personas?
- What: What capabilities needed?
- When: What triggers the need?
- Where: What context/environment?
- Why: What value/benefit?
4. User Story Definition
Format: As a [persona], I want [capability], so that [benefit]
Quality criteria:
- Specific persona identified
- Capability clearly stated
- Benefit/value articulated
- Testable outcome
5. Acceptance Criteria
For each story:
Given [context/precondition]
When [action/event]
Then [expected outcome]
Include:
- Happy path scenarios
- Error conditions
- Edge cases
- Non-functional requirements
6. Validation
Check:
- [ ] All stories have persona, capability, benefit
- [ ] Acceptance criteria are testable
- [ ] Edge cases identified
- [ ] Dependencies mapped
- [ ] Ambiguities flagged
User Story Template
### US{N}: {Story Title}
**As a** {specific persona}
**I want** {specific capability}
**So that** {specific benefit}
**Priority**: {P0/P1/P2}
**Complexity**: {S/M/L/XL}
**Acceptance Criteria**:
1. Given {context}, When {action}, Then {outcome}
2. Given {error condition}, When {action}, Then {error handling}
3. Given {edge case}, When {action}, Then {graceful handling}
**Non-Functional**:
- Performance: {requirement}
- Security: {requirement}
- Usability: {requirement}
**Dependencies**: {Other stories or systems}
**Assumptions**: {What we're assuming}
**Open Questions**: {What needs clarification}
Common Patterns
CRUD Operations:
- Create: As a user, I want to create X, so that I can track Y
- Read: As a user, I want to view X, so that I can understand Y
- Update: As a user, I want to edit X, so that I can correct Y
- Delete: As a user, I want to remove X, so that I can clean up Y
Authentication/Authorization:
- Login, logout, password reset
- Role-based access control
- Session management
Data Validation:
- Input validation
- Error messaging
- Constraint enforcement
Integration with Tools
# Search for similar requirements (FTS5 over indexed docs + wiki)
wicked-brain:search "user story"
# Store requirements on the active clarify task via native TaskUpdate
# TaskUpdate(taskId="{task_id}", description="{previous}\n\n## Requirements\n{user_stories}")
# Recall past patterns
Skill(skill="wicked-brain:memory", args="recall \"requirements for {feature_type}\"")
Output Format
See: refs/requirements-output-format-template.md, refs/requirements-example-auth.md, and refs/requirements-example-export-integration.md
Related Skills
mikeparcewski/wicked-garden-engineering-conformance-reviewer
development
VerifiedTrustedCommunity
Pattern-conformance agent-half: evaluates a produced artifact or diff against a set of architectural/design pattern rules from the conformance-rule store (wicked_governance schema). Returns structured findings with rule ID, severity, and rationale — the deterministic half (mechanical rule recall) is done by the guard pipeline; this is the semantic evaluation step. Triggered by: the guard_pipeline `outgov_pattern` check (session-close), or explicitly by an engineering review when WICKED_OUTGOV_RULES_DIR is populated. NOT a replacement for the full `engineering` review skill — focuses only on conformance to stored Pattern rules; architecture and code-quality checks live in the `engineering` skill. Semantic evaluation reuses `wicked-garden-qe-semantic-reviewer` as the designated agent-half evaluator (per garden#983 spec). This skill is the orchestrating wrapper that loads applicable Pattern rules and delegates the per-rule semantic judgment to qe-semantic-reviewer.
8SKILL.mdUpdated Jul 22, 2026
mikeparcewski/wicked-garden-domain
tools
VerifiedTrustedCommunity
The FOUNDATIONAL domain-model capability: extract a codebase's domain — testable business rules (with confidence + provenance), entities, requirements — as a schema-conformant model on the estate graph. The workers annotate the store; wicked-core reads it and builds the requirements graph, coverage-gating fail-closed. Steers three fork workers. A shared substrate, not a modernization tool. The `modernize` archetype DERIVES from it; build / migrate / review / specify / explore consume the SAME domain model — none OWN it. Understanding a codebase's domain is upstream of almost everything else garden does. Use when: "extract the business rules / domain model from this codebase", "build a requirements graph from the code", "what does this system actually require", "reverse-engineer the domain before we build/port/migrate". Works on ANY codebase (modern or legacy) — the value is the domain model, not the porting. NOT the code transform itself (that is the archetype consuming this model). This skill produces the DOMAIN MODEL, not new code.
8SKILL.mdUpdated Jul 15, 2026
mikeparcewski/wicked-garden-domain-modeler
development
VerifiedTrustedCommunity
Domain-graph fork worker for the modernize archetype. Groups the estate's Louvain communities into business domains, attaches each requirement to its cluster (advisory cluster_id provenance), and invokes wicked-core's domain-graph build (which reads the annotated estate store, recomputes coverage fail-closed, and builds the requirements graph) — then validates core's output against the vendored schema. Use when: dispatched by wicked-garden-domain after rule extraction to turn a flat rule set into cluster-keyed domains; "group these into domains", "build the requirements graph", "translate clusters into a domain model". NOT for mining the rules themselves (that is domain-extractor) or threat-modeling (that is domain-coverage).
8SKILL.mdUpdated Jul 15, 2026
mikeparcewski/wicked-garden-domain-extractor
tools
VerifiedTrustedCommunity
Rule-extraction fork worker for the FOUNDATIONAL domain-model capability. Mines testable business rules from a codebase — each with a numeric confidence and a provenance{source, ref, source_kinds} — and annotates them into the estate store so wicked-core can build the domain-model requirements graph (coverage-gated). This is a substrate, not a modernization tool: the `modernize` archetype DERIVES from it, and build / migrate / review / specify / explore can consume the same domain model — none OWN it. Use when: dispatched by wicked-garden-domain to mine the business_rules of a codebase (or a module); "extract the domain rules", "what does this system require", building the requirements half of a domain model. NOT for grouping into domains (that is domain-modeler) or judging coverage (that is domain-coverage — a seat-distinct evaluator).
8SKILL.mdUpdated Jul 15, 2026