zipsa-commands

Plugin zipsa-commands from marketplace zipsa-co-work in mojokb/zipsa-co-command. Commands read from the repo's manifest — 4 days ago.

Skills (9)

• zipsa-build

  Implement tasks incrementally with Codex as an approach reviewer. For each task, Agent and Codex independently design the implementation approach, compare, then Agent implements. Use after zipsa-tasks produces a task list. Pass the path to the tasks file or a single task description as the argument.

• zipsa-grill

  Grill the user with sharp, probing questions to pin down requirements, scope, constraints, and success criteria before planning. Use at the front of the workflow when the request is a vague idea. Asks one focused cluster at a time, challenges vague answers, and stops when no material ambiguity remai

• zipsa-plan

  Generate a parallel plan via Codex. Use when you want an additional planning perspective to compare against your own plan. Runs in the background so you can continue working in parallel. Results are documented only — does not proceed to implementation.

• zipsa-review

  Dual-perspective code review — Agent as Junior BE developer, Codex as Senior developer. Reviews code against SOLID, Clean Code, linting, readability, Python 40-line function limit excluding docstrings and Go 60-line limit, Google style docstring compliance. If REST API code is detected, also reviews

• zipsa-tasks

  Break a validated plan into concrete implementation tasks. Spawns Codex immediately, then collaborates with Codex on technical choices. Escalates user-owned decisions and material information/access gaps after evidence gathering. Once all decisions are made, both independently produce a task breakdo

• zipsa-test

  Verify a completed change against requirements with independent test design and executed unit, integration, or E2E checks as needed. Use after build, before code review, or to reverify review fixes. Report defects, blocked checks, and evidence; does not authorize product-code fixes or deployment.

• zipsa-think

  Bounce ideas off Codex. Use when you want fast alternative ideas, critiques, and perspectives on any topic. Triggers an interactive conversation with the Codex MCP server for brainstorming and exploration. Results are documented only — does not proceed to implementation.

• zipsa-validate

  Get a staff engineer review of your plan via Codex. Use when you want critical review feedback on a plan before finalizing it. Pass the path to the plan file as the argument.

• zipsa-workflow

  Advance fix or feature work through the existing zipsa stages, one stage per invocation. Track artifact-backed progress, approval gates, regression routes, and interruption recovery. Use to start, continue, or resume coordinated development; completion ends at implementation, testing, and code revie

Similar plugins