sequant 1.13.2 → 1.13.4

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "sequant",
   "description": "Structured workflow system for Claude Code - GitHub issue resolution with spec, exec, test, and QA phases",
-  "version": "1.13.2",
+  "version": "1.13.4",
   "author": {
     "name": "admarble",
     "email": "github@admarble.com"

package/README.md

@@ -9,27 +9,29 @@ Solve GitHub issues with structured phases and quality gates — from issue to m
 
 ## Quick Start
 
-### Option A: Install as Claude Code Plugin (Recommended)
+### Install via npm (Recommended)
 
 ```bash
-# Add the Sequant marketplace
-/plugin marketplace add admarble/sequant
-
-# Install the plugin
-/plugin install sequant
+# In your project directory
+npm install sequant
+npx sequant doctor   # Verify setup
 ```
 
-Then run setup:
-```
-/sequant:setup    # Initialize worktrees directory
+To update:
+```bash
+npm update sequant
 ```
 
-### Option B: Install via npm
+### Alternative: Install as Claude Code Plugin
+
+> **Note:** Plugin updates via `/plugin update` may not work reliably. Use `npm update sequant` to get latest skills.
 
 ```bash
-# In your project directory
-npx sequant init
-npx sequant doctor   # Verify setup
+# Add the Sequant marketplace
+/plugin marketplace add admarble/sequant
+
+# Install the plugin
+/plugin install sequant
 ```
 
 ### Start Using

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "sequant",
-  "version": "1.13.2",
+  "version": "1.13.4",
   "description": "Quantize your development workflow - Sequential AI phases with quality gates",
   "type": "module",
   "bin": {

package/templates/skills/solve/SKILL.md

@@ -20,7 +20,22 @@ When invoked as `/solve <issue-numbers>`, your job is to:
 1. Analyze the provided issue number(s)
 2. Check labels to determine issue type
 3. Recommend the optimal workflow sequence
-4. Display the recommended commands
+4. **Output using the EXACT template format** (see Output Template section)
+
+## CRITICAL: Output Requirements
+
+**You MUST follow the Output Template exactly.** Key requirements:
+
+1. **Use the ASCII box header** with `npx sequant run <ISSUES> <FLAGS>`
+2. **Include the Flags Table** showing ALL flags with ✓/✗:
+   - `-q` (quality-loop) — **Default to ✓** unless trivial bug fix
+   - `--chain` — ✓ if dependencies between issues
+   - `--qa-gate` — ✓ if chain with 3+ issues
+   - `--base` — ✓ if feature branch context
+   - `--testgen` — ✓ if new feature needs tests
+3. **Quality loop (`-q`) should be ✓ (enabled)** for most issues — only skip for simple bug fixes or docs-only changes
+
+**DO NOT** output free-form prose. Use the structured template.
 
 ## Behavior
 
@@ -62,8 +77,9 @@ Quality loop (`--quality-loop` or `-q`) provides automatic fix iterations when p
 - Labels include: `complex`, `refactor`, `breaking`, `major` (auto-enabled)
 - Labels include: `enhancement`, `feature` (new functionality)
 - Issue involves multiple files or components
-- Issue title contains: "add", "implement", "create", "refactor", "update"
+- Issue title contains: "add", "implement", "create", "refactor", "update", "overhaul", "redesign", "improve", "rework", "revamp", "migrate", "convert", "design", "build", "develop"
 - Issue is NOT a simple bug fix with `bug` or `fix` label only
+- **Default: recommend quality loop unless explicitly trivial** — most issues benefit from retry capability
 
 **Skip quality loop recommendation only when:**
 - Simple bug fix (only `bug` or `fix` label, no other labels)