Help us improve
Share bugs, ideas, or general feedback.
From dev-workflow
Executes end-to-end dev workflow: spec generation with user confirmation, implementation, refactoring, code review, and PR summary. Invoke with feature description or name.
npx claudepluginhub kzytateishi/spikeee-plugins-marketplace --plugin dev-workflowHow this skill is triggered — by the user, by Claude, or both
Slash command
/dev-workflow:dev-workflowThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Run the complete development workflow for `$ARGUMENTS`.
Enforces a gated Spec → Plan → Build → Test → Review → Ship lifecycle for multi-file features and projects, preventing AI coding agents from skipping specification and verification steps.
Guides technical evaluation of code review feedback: read fully, restate for understanding, verify against codebase, respond with reasoning or pushback before implementing.
Share bugs, ideas, or general feedback.
Run the complete development workflow for $ARGUMENTS.
Run all steps sequentially. By default, pause after Step 1 (specify) and present the spec to the user for confirmation before proceeding to implementation. Steps 2–5 run automatically, stopping only on gate failures.
Skip the specify confirmation only when the user explicitly requests it (e.g., "確認不要", "skip confirmation", "そのまま進めて").
Each step MUST pass its gate condition before proceeding to the next step.
Step 1: /specify → Generate specification + task list
GATE: user confirmation (default, skippable)
Step 2: /implement → Implement tasks from the specification
GATE: all tests, lint, and type checks pass
Step 3: /refactor → Iterative refactoring (3+ rounds)
GATE: all tests, lint, and type checks pass
Step 4: /code-review → Multi-perspective code review
GATE: no Critical or High findings remain
Step 5: /pr-summary → Generate PR description
If a gate fails, STOP the workflow and fix the issues before proceeding:
/code-review to verify. Do NOT proceed to Step 5 with unresolved Critical or High findings.Generate a specification document and task list for the feature described in $ARGUMENTS.
Read and follow the full process defined in specify/SKILL.md.
After generating the spec, present a summary to the user:
order.md and todo.mdThen ask the user to approve, request changes, or abort before proceeding.
Implement all tasks from the specification created in Step 1.
Read and follow the full process defined in implement/SKILL.md. Use the feature name derived from Step 1.
Run iterative refactoring on all changed files.
Read and follow the full process defined in refactor/SKILL.md.
Run a comprehensive code review on the current branch.
Read and follow the full process defined in code-review/SKILL.md.
Generate a pull request description from the changes.
Read and follow the full process defined in pr-summary/SKILL.md.
After all steps are done (or the user stops), summarize what was completed: