tweety53
@tweety53
Public Skills
flow
by tweety53
Single-command pipeline — brainstorm, implement behind the review panel resolved from the settings store, then integrate and archive across the same three-state pipeline, pausing only at the human gates. Re-run to resume, fix, or integrate. Use for /flow.
flow-contracts
by tweety53
The flow pipeline itself plus its contract definitions — the three states and their transitions, the state file shape, project configuration, Jira integration, follow-up issues, plan provenance, the build-green tag, and workspace isolation. Load the one file you need; each is canonical for its own contract, and a run never loads a rationale appendix. Referenced by the stubs in rules/flow-manual-review.mdc.
flow-self-review
by tweety53
Run the self-review pass a /flow or /flow-fast run deferred, inline on this session's model, from the saved context bundle; file, rate, write the report, delete the bundle. Standalone, not a pipeline stage. Use for /flow-self-review.
flow-settings
by tweety53
Read and change the harness-wide flow defaults — default model, reviewer slots and self-review model. Standalone, not a pipeline stage. Use for /flow-settings.
flow-fast
by tweety53
Minimal-ceremony /flow variant — one invocation from Jira key to landed change. A git worktree for isolation and nothing else, implementation and review panel as the plan's class decides, project lint plus targeted tests, then the project's default landing route and cleanup; no spectre artifacts, no state file. Use for /flow-fast.
flow-plan
by tweety53
Research mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements before or during a change. A captured session creates the change at STARTED and stops there. Use for /flow-plan.
flow-status
by tweety53
Show every open flow change with its pipeline state, PR, next command, and last update. Read-only. Use for /flow-status.