Create clear, testable specifications from natural language descriptions. Focus on what users need and why, not implementation details. Triggers: spec writing, feature specification, requirements documentation, user stories, acceptance criteria, success criteria, testable requirements Use when: creating new feature specifications, refining existing specifications, writing user stories and acceptance criteria, defining success criteria DO NOT use when: generating implementation tasks - use task-planning. DO NOT use when: executing implementation - use implementation-executor agent. Produces spec.md artifacts with user-focused, testable requirements.
/plugin marketplace add athola/claude-night-market/plugin install sanctum@claude-night-marketThis skill inherits all available tools. When active, it can use any tool Claude has access to.
modules/specification-structure.mdmodules/success-criteria-patterns.mdGuides the creation of clear, complete, and testable specifications from natural language feature descriptions. Specifications focus on user value and business needs, avoiding implementation details.
See: specification-structure module for detailed templates and guidelines
See: success-criteria-patterns module for detailed examples and conversion process
speckit-orchestrator: Workflow coordinationtask-planning: Converting specs to tasksThis skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.