- [Overview](#overview)
/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/command-skill-matrix.mdmodules/progress-tracking.mdmodules/writing-plans-extensions.mdCoordinates the Spec Driven Development workflow, skill loading, and progress tracking throughout the command lifecycle.
Treat SDD as a minimal, testable “self-modeling” loop:
spec.md, plan.md, tasks.md).specify/memory/constitution.md) + progress stateThis mirrors patterns from open-ended embodied agents (e.g., Voyager/MineDojo) that compound capability via a curriculum (tasks.md) and a skill library (reusable plugin skills + superpowers methodology skills).
/speckit-* command.Verify Repository Context
.specify/ directory structure.Load Persistent State ("presence")
.specify/memory/constitution.md for constraints/principles.spec.md / plan.md / tasks.md context if present.Load Command Dependencies
Initialize Progress Tracking
Quick reference for command-to-skill mappings:
| Command | Primary Skill | Complementary Skills |
|---|---|---|
/speckit-specify | spec-writing | brainstorming |
/speckit-clarify | spec-writing | brainstorming |
/speckit-plan | task-planning | writing-plans |
/speckit-tasks | task-planning | executing-plans |
/speckit-implement | - | executing-plans, systematic-debugging |
/speckit-analyze | - | systematic-debugging, verification |
/speckit-checklist | - | verification-before-completion |
For detailed patterns: See modules/command-skill-matrix.md for complete mappings and loading rules.
For each workflow session, track:
For detailed patterns: See modules/progress-tracking.md for TodoWrite patterns and metrics.
spec-writing: Specification creation and refinement.task-planning: Task generation and planning.superpowers:brainstorming: Idea refinement.superpowers:writing-plans: Implementation planning.superpowers:executing-plans: Task execution.Command not found Ensure all dependencies are installed and in PATH
Permission errors Check file permissions and run with appropriate privileges
Unexpected behavior
Enable verbose logging with --verbose flag
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 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 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.