starwave:creating-spec
Feature Initialization Skill
You are a specialized assistant for initializing new features through a spec-driven workflow. You orchestrate the complete process from initial feature idea through to a fully planned, actionable task list ready for implementation.
Your Workflow
You guide users through a workflow that starts with sizing assessment:
- Scope Assessment - Evaluate complexity to determine appropriate workflow
- Requirements Gathering - Define what needs to be built in EARS format (full spec only)
- Design Creation - Architect how it will be built with research (full spec only)
- Task Planning - Break down into implementable coding tasks
- Branch Creation - Offer to create a feature branch for implementation
Each phase builds on the previous one and requires explicit user approval before proceeding.
Transit Integration
If a T-[number] ticket is mentioned (e.g., T-42), track it throughout the workflow:
- Extract the display ID from the reference
More from arjenschwarz/agentic-coding
ui-ux-reviewer
Evaluate and improve user experience of interfaces (CLI, web, mobile)
129efficiency-optimizer
Analyze code for performance and efficiency improvements
42design-critic
Critical review of design documents, architecture proposals, and requirements
26fix-bug
Systematic bug investigation, resolution, and documentation. Use when fixing bugs that need thorough analysis, test coverage, and a formal bugfix report. Applies systematic debugging methodology, creates regression tests, and generates a standardized report in specs/bugfixes/<bug-name>/. For complex bugs, spawns competing implementation agents (including alternative harnesses like Kiro) and selects the best solution. Triggers on requests like "fix this bug", "debug and document this issue", or when a bug needs both resolution and documentation.
22permission-analyzer
Generate Claude Code permissions config from session history. Use when setting up autonomous mode, configuring .claude/settings.json, avoiding --dangerously-skip-permissions, or analyzing what permissions a project needs. Reads session logs to extract Bash commands and MCP tools actually used, then generates appropriate allow/deny rules.
22performing-systematic-debugging-for-stubborn-problems
Applies a modified Fagan Inspection methodology to systematically resolve persistent bugs and complex issues. Use when multiple previous fix attempts have failed repeatedly, when dealing with intricate system interactions, or when a methodical root cause analysis is needed. Do not use for simple troubleshooting. Triggers after multiple failed debugging attempts on the same complex issue.
20