specwright/templates/skills/skill/SKILL.md
--- name: [SKILL_NAME] description: "[SKILL_DESCRIPTION] Use when: (1) [TRIGGER_1], (2) [TRIGGER_2], (3) [TRIGGER_3]" version: 1.0 created: [CURRENT_DATE] encoding: UTF-8 [globs_section] always_apply: [false_or_true] --- # [SKILL_NAME] > [LONGER_DESCRIPTION_OF_WHAT_THIS_SKILL_PROVIDES] ## Activation This skill activates via: - **Auto-Load**: For files matching `[GLOB_PATTERNS]` - **Explicit**: When explicitly invoked by name - **Always**: [always_apply value] ### File Patterns (Auto-Load)
npx skillsauth add michsindlinger/specwright specwright/templates/skills/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.
[LONGER_DESCRIPTION_OF_WHAT_THIS_SKILL_PROVIDES]
This skill activates via:
[GLOB_PATTERNS]This skill is automatically loaded when working with files matching:
globs:
[GLOB_LIST]
Examples:
[PATTERN_EXAMPLE_1][PATTERN_EXAMPLE_2]To invoke this skill explicitly, reference it by name: [SKILL_NAME]
| Server | Purpose | Required | |--------|---------|----------| | [MCP_SERVER_1] | [PURPOSE] | Yes/No | | [MCP_SERVER_2] | [PURPOSE] | Yes/No |
mcp_tools:
- server: [MCP_SERVER_NAME]
tools:
- [TOOL_NAME_1] # [BRIEF_DESCRIPTION]
- [TOOL_NAME_2] # [BRIEF_DESCRIPTION]
{
"mcpServers": {
"[MCP_SERVER_NAME]": {
"command": "[COMMAND]",
"args": ["[ARG_1]", "[ARG_2]"],
"env": {
"[ENV_VAR]": "[VALUE]"
}
}
}
}
Using [MCP_TOOL_1]:
mcp__[server]__[tool] with parameters:
- param1: [DESCRIPTION]
- param2: [DESCRIPTION]
[DESCRIPTION_OF_COMPETENCY]
Key Principles:
[DESCRIPTION_OF_COMPETENCY]
Key Principles:
[PRACTICE_1]
[PRACTICE_2]
| Anti-Pattern | Problem | Solution | |--------------|---------|----------| | [ANTI_PATTERN_1] | [WHY_IT_IS_BAD] | [WHAT_TO_DO_INSTEAD] | | [ANTI_PATTERN_2] | [WHY_IT_IS_BAD] | [WHAT_TO_DO_INSTEAD] | | [ANTI_PATTERN_3] | [WHY_IT_IS_BAD] | [WHAT_TO_DO_INSTEAD] |
Context: [WHEN_TO_USE_THIS]
// [DESCRIPTION]
[CODE_EXAMPLE]
Context: [WHEN_TO_USE_THIS]
// [DESCRIPTION]
[CODE_EXAMPLE]
| Skill | Relationship | |-------|--------------| | [SKILL_1] | [HOW_THEY_WORK_TOGETHER] | | [SKILL_2] | [HOW_THEY_WORK_TOGETHER] |
| Skill | Conflict | Resolution | |-------|----------|------------| | [SKILL_1] | [CONFLICT_DESCRIPTION] | [HOW_TO_RESOLVE] |
Skill generated by Specwright DevTeam Builder Framework: [FRAMEWORK] Created: [CURRENT_DATE]
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