Create, manage, and track specifications through their full lifecycle from draft to completion. Use when user wants to plan features, create specs, check progress, activate work, or complete specifications.
Creates and manages specifications through a 3-folder lifecycle system (draft/active/completed). Auto-activates when you describe features, request specs, or ask about progress.
/plugin marketplace add jeanluciano/quaestor/plugin install quaestor@quaestorThis skill is limited to using the following tools:
LIFECYCLE.mdTEMPLATE.mdWRITING.mdI help you work with specifications: creating new specs from requirements, managing their lifecycle (draft → active → completed), and tracking progress automatically.
Auto-activate when:
/quaestor:plan slash commandDo NOT auto-activate when:
New to specs? Just describe what you want to build:
"I want to add email notifications when orders are placed"
I'll ask a few questions, then create a complete specification for you.
Have specs already? Tell me what you need:
"Show me my active specs"
"Activate spec-feature-003"
"What's the progress on spec-auth-001?"
I detect what you need and adapt automatically:
When you describe a feature or ask me to create a spec, I:
spec-feature-001).quaestor/specs/draft/[spec-id].mdSee @WRITING.md for the complete specification template and writing process
When you ask about spec status or want to move specs, I:
See @LIFECYCLE.md for folder-based lifecycle management and progress tracking
Specifications live in folders that represent their state:
.quaestor/specs/
├── draft/ # New specs (unlimited)
├── active/ # Work in progress (MAX 3)
└── completed/ # Finished work (archived)
The folder IS the state - no complex tracking needed!
Why max 3 active? Forces focus on finishing work before starting new features.
I provide just enough information for your current task, with details available when needed:
Minimal workflow (I guide you):
You: "Add user authentication"
Me: I'll ask 3-5 questions
Me: Create spec-feature-001.md in draft/
Common operations:
"Show active specs" → List with progress bars"Activate spec-feature-003" → Move draft/ → active/"Complete spec-auth-001" → Move active/ → completed/When you need more details:
✅ Auto-generate unique IDs ✅ Forgiving template (auto-corrects common mistakes) ✅ No placeholders - only real values ✅ Rich metadata (priority, type, timestamps)
✅ Folder-based states (simple and visual) ✅ 3-active-spec limit (enforced automatically) ✅ Progress calculation from checkboxes ✅ Metadata updates on state changes
✅ Parse checkbox completion: - [x] vs - [ ]
✅ Calculate percentage: 4/5 complete = 80%
✅ Visual progress bars
✅ Branch linking support
Creating specs:
.quaestor/specs/draft/[spec-id].mdManaging specs:
Once you have specifications:
/impl spec-feature-001 or implementing-features skillI handle both creation and management of specifications. Just tell me what you need - I'll detect the mode and guide you through it with minimal upfront context.
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 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.