codyswanngt/acceptance-criteria
plugins/lisa-cursor/skills/acceptance-criteria/SKILL.md
Acceptance criteria definition. Gherkin user flows (Given/When/Then), error states, UX concerns, and empirical verification from the user perspective.
$ install --global
skillsauthnpx skillsauth add codyswanngt/lisa acceptance-criteriaInstall 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 12, 2026, 3:02 AM4.2s1 file scanned
SKILL.md
- name:
- acceptance-criteria
- description:
- Acceptance criteria definition. Gherkin user flows (Given/When/Then), error states, UX concerns, and empirical verification from the user perspective.
Acceptance Criteria
Evaluate changes from a non-technical user's perspective. Define acceptance criteria and verify behavior matches requirements.
Analysis Process
- Understand the user goal -- what problem does this solve for the end user?
- Define user flows -- step-by-step paths through the feature, including happy path and error paths
- Write acceptance criteria -- testable conditions from the user's perspective
- Identify UX concerns -- confusing interactions, missing feedback, accessibility issues
- Map error states -- what happens when things go wrong, and what the user sees
- Run the feature -- execute scripts, call APIs, or trigger the described behavior to verify empirically
- Compare output to requirements -- does actual behavior match expectations?
Output Format
Structure findings as:
## Product Analysis
### User Goal
[1-2 sentence summary of what the user wants to accomplish]
### User Flows (Gherkin)
#### Happy Path
Given [precondition]
When [action]
Then [expected outcome]
#### Error Path: [description]
Given [precondition]
When [action that fails]
Then [error handling behavior]
### Acceptance Criteria
- [ ] [criterion from user perspective]
### UX Concerns
- [concern] -- impact on user experience
### Error Handling Requirements
| Error Condition | User Sees | User Can Do |
|----------------|-----------|-------------|
### Verification Results
For each acceptance criterion:
- **Criterion:** [what was expected]
- **Result:** Pass / Fail / Not Yet Testable
- **Evidence:** [what was observed]
### Out of Scope
- [thing that might be expected but is not part of this work]
Rules
- Write acceptance criteria from the user's perspective, not the developer's
- Every user flow must include at least one error path
- Use Gherkin format (Given/When/Then) for user flows to enable direct translation into test cases
- When verifying, always run the feature -- never review by only reading code
- If you cannot run the feature (missing dependencies, services unavailable), report as a blocker -- do not guess
- If the changes are purely internal (refactoring, config, tooling), report "No user-facing impact" and explain why
- Do not propose UX changes beyond what was described -- flag scope concerns instead
- Assume the reviewer has no technical background
Related Skills
codyswanngt/plugins/src/harper-fabric/skills/harper-realtime
tools
VerifiedTrustedCommunity
--- name: harper-realtime description: This skill should be used when adding or troubleshooting Harper (HarperDB/Fabric) real-time behavior: MQTT topics, WebSocket resource subscriptions, resource publish/subscribe handlers, SSE-style streaming routes, and local subscriber verification. Pairs with harper-resources, harper-config-yaml, harper-schema-graphql, and harper-build-and-deploy. --- # Harper Realtime ## Overview Harper exposes live data through the same Resource model used for REST and
1SKILL.mdUpdated Jun 13, 2026
codyswanngt/plugins/lisa-harper-fabric/skills/harper-realtime
tools
VerifiedTrustedCommunity
--- name: harper-realtime description: This skill should be used when adding or troubleshooting Harper (HarperDB/Fabric) real-time behavior: MQTT topics, WebSocket resource subscriptions, resource publish/subscribe handlers, SSE-style streaming routes, and local subscriber verification. Pairs with harper-resources, harper-config-yaml, harper-schema-graphql, and harper-build-and-deploy. --- # Harper Realtime ## Overview Harper exposes live data through the same Resource model used for REST and
1SKILL.mdUpdated Jun 13, 2026
codyswanngt/plugins/lisa-harper-fabric-cursor/skills/harper-realtime
tools
VerifiedTrustedCommunity
--- name: harper-realtime description: This skill should be used when adding or troubleshooting Harper (HarperDB/Fabric) real-time behavior: MQTT topics, WebSocket resource subscriptions, resource publish/subscribe handlers, SSE-style streaming routes, and local subscriber verification. Pairs with harper-resources, harper-config-yaml, harper-schema-graphql, and harper-build-and-deploy. --- # Harper Realtime ## Overview Harper exposes live data through the same Resource model used for REST and
1SKILL.mdUpdated Jun 13, 2026
codyswanngt/plugins/lisa-harper-fabric-copilot/skills/harper-realtime
tools
VerifiedTrustedCommunity
--- name: harper-realtime description: This skill should be used when adding or troubleshooting Harper (HarperDB/Fabric) real-time behavior: MQTT topics, WebSocket resource subscriptions, resource publish/subscribe handlers, SSE-style streaming routes, and local subscriber verification. Pairs with harper-resources, harper-config-yaml, harper-schema-graphql, and harper-build-and-deploy. --- # Harper Realtime ## Overview Harper exposes live data through the same Resource model used for REST and
1SKILL.mdUpdated Jun 13, 2026