Sequant

Workflow automation for Claude Code.

Solve GitHub issues with structured phases and quality gates — from issue to merge-ready PR.

Quick Start

# In your project directory
npx sequant init
npx sequant doctor   # Verify setup

Then in Claude Code:

/fullsolve 123    # Solve issue #123 end-to-end

Or step-by-step:

/spec 123    # Plan implementation
/exec 123    # Build in isolated worktree
/qa 123      # Review before merge

Prerequisites

• Claude Code — AI coding assistant
• GitHub CLI — run gh auth login
• Node.js 18+ and Git

How It Works

Sequant adds slash commands to Claude Code that enforce a structured workflow:

┌─────────┐    ┌─────────┐    ┌─────────┐    ┌─────────┐
│  /spec  │───▶│  /exec  │───▶│  /test  │───▶│   /qa   │───▶ Merge
└─────────┘    └─────────┘    └─────────┘    └─────────┘
     │              │              │              │
     ▼              ▼              ▼              ▼
   Plan          Build        Verify (UI)     Review

/test is optional — used for UI features when Chrome DevTools MCP is available.

Quality Gates

Every /qa runs automated checks:

• AC Adherence — Code verified against acceptance criteria
• Type Safety — Detects any, as any, missing types
• Security Scans — OWASP-style vulnerability detection
• Scope Analysis — Flags changes outside issue scope

When checks fail, /loop automatically fixes and re-runs (up to 3x).

Two Ways to Use

Interactive (Claude Code)

Type commands directly in Claude Code chat:

/fullsolve 123              # Complete pipeline
/spec 123 → /exec → /qa     # Step by step

Headless (CLI)

Run without Claude Code UI:

npx sequant run 123              # Single issue
npx sequant run 1 2 3            # Batch (parallel)
npx sequant run 123 --quality-loop
npx sequant run 123 --base feature/dashboard  # Custom base branch

Commands

Core Workflow

| Command | Purpose | |---------|---------| | /spec | Plan implementation, draft acceptance criteria | | /exec | Implement in isolated git worktree | | /test | Browser-based UI testing (optional) | | /qa | Code review and quality gate |

Automation

| Command | Purpose | |---------|---------| | /fullsolve | Complete pipeline in one command | | /solve | Recommend optimal workflow for issue | | /loop | Fix iteration when checks fail |

Integration

| Command | Purpose | |---------|---------| | /merger | Multi-issue integration and merge | | /testgen | Generate test stubs from spec | | /verify | CLI/script execution verification |

Utilities

| Command | Purpose | |---------|---------| | /assess | Issue triage and status assessment | | /docs | Generate feature documentation | | /clean | Repository cleanup | | /security-review | Deep security analysis | | /reflect | Workflow improvement analysis |

CLI Commands

npx sequant init              # Initialize in project
npx sequant update            # Update skill templates
npx sequant doctor            # Check installation
npx sequant status            # Show version and config
npx sequant run <issues...>   # Execute workflow

See Run Command Options for advanced usage.

Configuration

// .sequant/settings.json
{
  "run": {
    "qualityLoop": false,
    "maxIterations": 3,
    "defaultBase": "feature/dashboard"  // Optional: custom default base branch
  }
}

See Customization Guide for all options.

Platform Support

| Platform | Status | |----------|--------| | macOS | ✅ Full support | | Linux | ✅ Full support | | Windows WSL | ✅ Full support | | Windows Native | ⚠️ CLI only |

Documentation

• Getting Started
• Workflow Concepts
• Run Command
• Feature Branch Workflows
• Customization
• Troubleshooting

Stack guides: Next.js · Rust · Python · Go

License

MIT