specwright/templates/skills/generic-skill/SKILL.md
# Generic Skill Template > Skill: [SKILL_NAME] > Role: [AGENT_ROLE] > Created: [DATE] > Version: 1.0.0 ## Purpose [Clear description of what this skill enables the agent to do] ## When to Activate This Skill **Trigger Conditions:** - [Condition 1] - [Condition 2] - [Condition 3] **Context Signals:** - "[Keyword or phrase that indicates need]" - "[File pattern or code pattern]" - "[User request pattern]" ## Core Capabilities ### 1. [Capability Name] [What this capability does] **Specific
npx skillsauth add michsindlinger/specwright specwright/templates/skills/generic-skillInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Skill: [SKILL_NAME] Role: [AGENT_ROLE] Created: [DATE] Version: 1.0.0
[Clear description of what this skill enables the agent to do]
Trigger Conditions:
Context Signals:
[What this capability does]
Specific actions:
[What this capability does]
Specific actions:
[What this capability does]
Specific actions:
[TECH_STACK_SPECIFIC]
For [FRAMEWORK/LIBRARY_NAME]:
[MCP_TOOLS]
<!-- Populated during skill creation based on: 1. User's installed MCP servers 2. User's selection for this skill Recommended for this skill (examples): - [MCP tool suggestions based on skill domain] Note: Skills work without MCP servers, but functionality may be limited -->[WORKFLOW_TOOLS]
<!-- Optional: Related workflows or templates -->When using this skill, ensure:
Scenario: [Description]
Approach:
[Code example or step-by-step approach]
Scenario: [Description]
Approach:
[Code example or step-by-step approach]
1. DETECT: [Trigger condition]
2. ANALYZE: [What to analyze]
3. PLAN: [Planning step]
4. EXECUTE: [Implementation]
5. VERIFY: [Verification]
6. DOCUMENT: [Documentation]
Template Usage Instructions:
This generic template should be used when:
Customization:
tools
Session Handoff: Erstellt eine vollständige Zusammenfassung der aktuellen Session für einen sauberen Kontextwechsel. NUR bei explizitem Aufruf (/session-handoff). NICHT automatisch auslösen. Geeignet wenn der User die Session resetten will, den Kontext aufräumen will, oder bei ~120k Tokens angelangt ist.
development
Pre-Mortem Risk Analysis: Strukturierte Prospective-Hindsight-Übung um launch-blocking Risiken vor Commitment aufzudecken. Team stellt sich vor, das Produkt sei 14 Tage nach Launch gefloppt, und arbeitet rückwärts. Klassifiziert Risiken in Tigers (echt), Paper Tigers (hypothetisch), Elephants (unausgesprochen). Nutze diesen Skill vor Build-Commitment, bei zu hoher Stakeholder-Confidence, vor Major-Releases, oder wenn das Team vage Sorgen nicht artikulieren kann. Trigger: /pre-mortem, 'pre-mortem', 'risk analysis', 'was könnte schiefgehen', 'risiken vor launch'.
testing
Six-Sigma Atomicity Validator for create-spec stories
tools
UX pattern definition guidance for navigation, user flows, interactions, and accessibility