cstack

VerifiedSafe

Codex workflow stack inspired by gstack, with explicit modes for planning, review, shipping, QA, and retros.

Sby Skills Guide Bot
DevelopmentIntermediate
107/25/2026
Claude CodeCursorWindsurfCopilotCodex
#workflow#structured-process#planning#review#codex

Recommended for

Our review

This skill introduces a structured workflow with explicit phases (planning, review, shipping, QA, retro) to guide development with an AI agent.

Strengths

  • Reduces ambiguity by sequencing decisions
  • Encourages thorough thinking before implementation
  • Provides clear roles for each step
  • Facilitates traceability and continuous improvement

Limitations

  • May feel too rigid for simple or repetitive tasks
  • Requires discipline to follow all phases
  • Does not replace human communication
When to use it

Use this skill for complex or multi-step projects where a structured approach minimizes errors and improves quality.

When not to use it

Avoid this skill for quick, one-off questions that do not require planning or review.

Security analysis

Safe
Quality score85/100

The skill only provides a workflow selection guide without executing any system commands or external actions, so it poses no execution risk.

No concerns found

Examples

Plan a new feature with product review
We need to add a dark mode to our app. Let's start with the product review phase to clarify user needs and scope.
Request a code review
Please review this pull request for bugs and regressions, using the review phase of cstack.
Ship a branch with confidence
I have a branch ready for merge. Run the ship phase: clean checks, change notes, and release confidence.

name: cstack description: Codex workflow stack inspired by gstack, with explicit modes for planning, review, shipping, QA, and retros.

cstack

Use this meta-skill when the user asks for a structured workflow rather than ad-hoc implementation.

Sub-skills

  • plan-product-review: clarify the real user problem, outcome, and scope boundaries before implementation.
  • plan-eng-review: define architecture, data flow, failure modes, and test matrix before coding.
  • review: perform bug- and regression-focused code review with severity and concrete references.
  • ship: prepare a branch for merge with clean checks, clear change notes, and release confidence.
  • qa: execute a lightweight but explicit validation plan and report evidence plus risk.
  • retro: summarize wins, misses, and concrete next improvements after shipping.

Selection guide

  • If the user request is about what to build, start with plan-product-review.
  • If the user request is about how to build safely, use plan-eng-review.
  • If the user asks for "review", default to review.
  • If the user asks to finalize and deliver, use ship.
  • If the user asks to test behavior, use qa.
  • If the user asks for lessons learned, use retro.
Related skills