A development workflow harness for Claude Code that covers system design, planning, implementation, end-to-end tests, and auto-run delivery from a raw requirement to a pull request. It also offers Codex integration.
@heliohqSystem-design thinking before any doc or code: goals/non-goals, back-of-envelope numbers, components and contracts, failure…
@heliohqRun Ship's full production workflow from raw requirement to PR: design, dev, E2E, review, QA, refactor, and handoff. Use only for…
@heliohqPlan implementation before coding: investigate the repo, write spec and plan, and validate with a peer. Use for "plan", "design…
@heliohqImplement from a spec or plan: extract stories, build in safe waves, test, commit, and get peer review per story. Use for…
@heliohqAdd durable end-to-end tests for user/API-visible behavior. Detect or scaffold the E2E framework, write tests, run the app, and…
@heliohqShip completed work: verify locally, commit related changes, push, create or update the PR, watch CI/reviews, and fix until…
@heliohqRuntime QA of a change: start the app, test acceptance criteria and edge cases, and report evidence. Use for "test this", "QA",…
@heliohqImprove existing code without changing behavior: scan smells, simplify, dedupe, reuse utilities, and verify after edits. Use for…
@heliohqStatic code review of the active diff: trace changed paths and report concrete P1/P2/P3 correctness, security, or spec bugs with…
@heliohqRoute ambiguous software-delivery requests to the smallest useful Ship workflow: one skill, a phase bundle, or /ship:auto. Use at…
@heliohqCreate or update structured docs under docs/ with frontmatter, numbering, lifecycle status, and index regeneration — guides,…
@heliohqIs this you? Claim your profilePut a plugin at the top of Plugins, from $9
