Skip to content

Your First Workflow

Walk through solving a GitHub issue with Sequant.

Sequant transforms GitHub issues into working code through sequential phases:

  1. Spec — Plan the implementation
  2. Exec — Build in an isolated worktree
  3. QA — Review against acceptance criteria

Pick a GitHub issue from your repository. For your first workflow, choose something small like a bug fix or simple feature.

Terminal window
# List open issues
gh issue list
# View issue details
gh issue view 123

Open Claude Code in your project, then run:

Terminal window
/spec 123

This command:

  • Reads the issue description and comments
  • Analyzes the codebase
  • Drafts an implementation plan with acceptance criteria
  • Posts the plan as a GitHub issue comment for your review

Review the plan before proceeding. Comment on the issue if you want changes.

Once you’re satisfied with the plan:

Terminal window
/exec 123

This command:

  • Creates an isolated git worktree (feature/123-issue-title)
  • Implements the changes according to the plan
  • Runs tests (npm test)
  • Creates commits with progress updates

After implementation:

Terminal window
/qa 123

This command:

  • Reviews code against acceptance criteria
  • Checks for type safety issues
  • Scans for security vulnerabilities
  • Flags scope creep (changes outside the issue)
  • Suggests fixes if issues are found

If QA passes, merge the feature branch:

Terminal window
# Create a pull request
gh pr create --fill
# Or merge directly (if your workflow allows)
git checkout main
git merge feature/123-issue-title

For simpler issues, use /fullsolve to run all phases:

Terminal window
/fullsolve 123

This runs spec → exec → qa with automatic fix iterations.

Your first workflow should be a simple issue. Complex refactors can wait until you’re familiar with the phases.

The /spec phase is your opportunity to shape the implementation. Review the plan carefully before /exec.

Sequant creates isolated worktrees so your main branch stays clean. If something goes wrong, you can safely delete the worktree.

If QA finds issues:

Terminal window
/loop 123

This automatically fixes issues found during QA and re-runs checks.