Skip to content

Commands Reference

thitichaya edited this page May 2, 2026 · 8 revisions

Commands Reference

Main Entry Point

/helix [phase]

Without arguments — shows the interactive phase menu.
With a phase name — invokes that skill directly.


All Commands

/helix or /helix menu

Opens the interactive phase selection menu.


/helix full

Runs the complete workflow from start to finish:

Step 0: intake → Step 1: repo check → Step 2: analyze →
Step 3: plan → Step 4: execute → Step 5: test →
Step 6: deploy → Step 7: finalize

Asks for the repo and feature description before starting. Each phase waits for user confirmation before proceeding to the next.


/helix analyze

Requirements breakdown and risk analysis.

Produces:

  • 5-dimension requirement breakdown (Functional / Non-functional / Technical / Constraints / Out-of-scope)
  • Risk table with Severity, Probability, Impact, Mitigation, Cost columns

Asks: repo location + what to build


/helix plan

Creates a structured development plan using the team's MD template.

Produces: a Markdown plan file with 5 phases (Setup, Development, Testing, Review, Deployment) + Risk Register + Cost Analysis

Process: 3-round internal review before presenting to user — Completeness → Technical soundness → Risk & cost

Requires: user approval + path to commit plan before continuing


/helix execute

Implements the approved plan.

Behaviors:

  • Asks which phase to start from
  • Creates a feature branch automatically
  • Reports progress every 10 minutes as a table
  • Runs a mandatory 3-round bug-fix loop after implementation (Logic → Integration → Security)

Will not proceed to tests without completing the bug-fix loop.


/helix test

Opens the test type selection menu. Run individual test types directly:

Command Type
/helix test-unit Unit tests
/helix test-integration Integration tests
/helix test-e2e E2E via Playwright
/helix test-perf Performance (k6 / autocannon / locust)
/helix test-security OWASP Top 10 + static analysis

Each sub-command checks the repo's existing test structure and adds to it rather than replacing it.


/helix deploy

Staging-first deployment workflow.

Flow:

  1. Pre-deploy checklist (tests pass, lint clean, migrations ready, rollback plan)
  2. Deploy to staging
  3. Run smoke tests
  4. Show results + wait for explicit production approval
  5. Deploy to production
  6. Post-deploy verification + environment separation audit

Never deploys to production without user confirmation.


/helix review

Code review and security audit.

Covers: Code quality, security (OWASP), performance, breaking changes, test coverage, architecture

Output format: ✅ Good / 🚫 Must Fix / ⚠️ Should Fix / 💡 Suggestions + metrics table + go/no-go decision


Argument Shorthand

All phases accept the short form as an argument to /helix:

/helix analyze     →  invokes helix:analyze
/helix plan        →  invokes helix:plan
/helix execute     →  invokes helix:execute
/helix test        →  invokes helix:test
/helix deploy      →  invokes helix:deploy
/helix review      →  invokes helix:review
/helix full        →  invokes helix:full

Clone this wiki locally