Menu
Create a new implementation plan document. Usage: /create-plan TITLE (e.g. /create-plan redis-adapter)
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Provides expertise in the message package architecture for building CloudEvents-based pipelines in gopipe. Apply when working with the message package, Engine, Router, Handler, Matcher, or designing event-driven systems.
Add an entry to the CHANGELOG under [Unreleased]. Usage: /changelog TYPE DESC (e.g. /changelog Added support for Redis adapter)
Create a new Architecture Decision Record. Usage: /create-adr TITLE (e.g. /create-adr add-redis-adapter)
Create a new feature branch from develop. Usage: /create-feature NAME (e.g. /create-feature message-validation)
Provides Go development standards and best practices for the gopipe codebase. Apply when writing or reviewing Go code: testing patterns, godoc, error handling, API conventions, and common anti-patterns to avoid.
Check documentation quality and consistency across the project.
| name | create-plan |
| description | Create a new implementation plan document. Usage: /create-plan TITLE (e.g. /create-plan redis-adapter) |
Create an implementation plan for: $ARGUMENTS
Follow the procedure: @../docs/procedures/planning.md
docs/plans/README.md to determine the next number (look at archive/ for highest used)docs/plans/<descriptive-name>.md (active plans use descriptive names, not numbers)Status: ProposedOverview: brief descriptionGoals: list of goalsTasks: one task section per major work itemImplementation Order: dependency diagram or listAcceptance Criteria: completion checklistdocs/plans/README.md index with the new plan under the current initiatives tableUse the title from arguments to derive the descriptive filename (lowercase, hyphens).