sequant 1.1.0 → 1.1.2

package/templates/skills/exec/SKILL.md

@@ -65,6 +65,24 @@ Invocation:
 - `/exec <freeform description>`:
   - Treat the text as a lightweight description + AC if no issue context is available.
 
+### 0. Pre-flight Check (After Context Restoration)
+
+**CRITICAL:** If continuing from a restored/summarized conversation, verify git state first:
+
+```bash
+# Check current state - are we in a worktree or main repo?
+pwd
+git log --oneline -3 --stat
+
+# Check for existing PRs or branches for this issue
+gh pr list --search "<issue-number>"
+git branch -a | grep -i "<issue-number>"
+```
+
+**Why this matters:** After context restoration, PRs may have merged, branches may have changed, or work may already be complete. Always verify before creating duplicate work.
+
+**If PR already merged:** The issue may be complete - verify and close if so.
+
 ### 1. Check Implementation Readiness
 
 **FIRST STEP:** Review the issue readiness and proceed with implementation.
@@ -416,3 +434,17 @@ At the end of a session:
      ```
 
 You may be invoked multiple times for the same issue. Each time, re-establish context, ensure you're in the correct worktree, and continue iterating until we are as close as practical to meeting the AC.
+
+---
+
+## Output Verification
+
+**Before responding, verify your output includes ALL of these:**
+
+- [ ] **AC Progress Summary** - Which AC items are satisfied, partially met, or blocked
+- [ ] **Files Changed** - List of key files modified
+- [ ] **Test/Build Results** - Output from `npm test` and `npm run build`
+- [ ] **Progress Update Draft** - Formatted comment for GitHub issue
+- [ ] **Next Steps** - Clear guidance on remaining work
+
+**DO NOT respond until all items are verified.**

package/templates/skills/fullsolve/SKILL.md

@@ -90,6 +90,32 @@ When invoked as `/fullsolve <issue-number>`, execute the complete issue resoluti
 /fullsolve 218 --max-iterations 5 # Override max fix iterations
 ```
 
+## Phase 0: Pre-flight Checks
+
+**CRITICAL after context restoration:** Before starting any work, verify the current git state to avoid duplicate work.
+
+### 0.1 Git State Verification
+
+```bash
+# Check current branch and recent commits
+git log --oneline -5 --stat
+
+# Check for any existing work on this issue
+git branch -a | grep -i "<issue-number>"
+gh pr list --search "<issue-number>"
+```
+
+**Why this matters:** After context restoration from a summarized conversation, the git state may have changed (PRs merged, rebases, etc.). Always verify what's already been done before creating files or making changes.
+
+### 0.2 Existing Work Detection
+
+Before creating any files, check if they already exist:
+- Look for test files: `ls -la src/**/*.test.ts`
+- Check recent commits for relevant changes
+- Verify PR status if one was mentioned in context
+
+**If work already exists:** Skip to the appropriate phase (e.g., if implementation is done, go to Phase 3 or 4).
+
 ## Phase 1: Planning (SPEC)
 
 Execute the planning phase inline (not as separate command):
@@ -479,3 +505,19 @@ For multiple issues, run `/fullsolve` on each sequentially:
 ```
 
 Each issue gets its own worktree, PR, and quality validation.
+
+---
+
+## Output Verification
+
+**Before responding, verify your output includes ALL of these:**
+
+- [ ] **Progress Table** - Phase, iterations, and status for each phase
+- [ ] **AC Coverage** - Each AC marked MET/PARTIALLY_MET/NOT_MET
+- [ ] **Quality Metrics** - Tests passed, build status, type issues
+- [ ] **Iteration Summary** - Test loop and QA loop iteration counts
+- [ ] **Final Verdict** - READY_FOR_MERGE, AC_MET_BUT_NOT_A_PLUS, or AC_NOT_MET
+- [ ] **PR Link** - Pull request URL (if created)
+- [ ] **Final GitHub Comment** - Summary posted to issue
+
+**DO NOT respond until all items are verified.**

package/templates/skills/loop/SKILL.md

@@ -311,3 +311,17 @@ Please run /exec <N> first to create the worktree.
 **Max iterations:** 3 (prevents infinite loops)
 **Re-validation after each fix:** Required
 **GitHub comment:** Posted after loop completion
+
+---
+
+## Output Verification
+
+**Before responding, verify your output includes ALL of these:**
+
+- [ ] **Iteration Progress** - Current iteration X/3
+- [ ] **Issues from Previous Phase** - List of issues being fixed
+- [ ] **Fixes Applied** - Each fix with file:line location
+- [ ] **Re-validation Results** - Tests/build/AC status after fixes
+- [ ] **Final Status** - FIXED, NEEDS_MORE_WORK, or MAX_ITERATIONS_REACHED
+
+**DO NOT respond until all items are verified.**

package/templates/skills/qa/SKILL.md

@@ -277,3 +277,70 @@ fi
 
 /qa 558  # Re-run, now sees verification, can give READY_FOR_MERGE
 ```
+
+---
+
+## Output Verification
+
+**Before responding, verify your output includes ALL of these:**
+
+- [ ] **AC Coverage** - Each AC item marked as MET, PARTIALLY_MET, or NOT_MET
+- [ ] **Verdict** - One of: READY_FOR_MERGE, AC_MET_BUT_NOT_A_PLUS, AC_NOT_MET
+- [ ] **Quality Metrics** - Type issues, deleted tests, files changed, additions/deletions
+- [ ] **Code Review Findings** - Strengths, issues, suggestions
+- [ ] **Next Steps** - Clear, actionable recommendations
+
+**DO NOT respond until all items are verified.**
+
+## Output Template
+
+You MUST include these sections:
+
+```markdown
+## QA Review for Issue #<N>
+
+### AC Coverage
+
+| AC | Description | Status | Notes |
+|----|-------------|--------|-------|
+| AC-1 | [description] | MET/PARTIALLY_MET/NOT_MET | [explanation] |
+| AC-2 | [description] | MET/PARTIALLY_MET/NOT_MET | [explanation] |
+
+**Coverage:** X/Y AC items fully met
+
+---
+
+### Quality Metrics
+
+| Metric | Value | Status |
+|--------|-------|--------|
+| Type issues (`any`) | X | OK/WARN |
+| Deleted tests | X | OK/WARN |
+| Files changed | X | OK/WARN |
+| Lines added | +X | - |
+| Lines deleted | -X | - |
+
+---
+
+### Code Review
+
+**Strengths:**
+- [Positive findings]
+
+**Issues:**
+- [Problems found]
+
+**Suggestions:**
+- [Improvements recommended]
+
+---
+
+### Verdict: [READY_FOR_MERGE | AC_MET_BUT_NOT_A_PLUS | AC_NOT_MET]
+
+[Explanation of verdict]
+
+### Next Steps
+
+1. [Action item 1]
+2. [Action item 2]
+```

package/templates/skills/reflect/SKILL.md

@@ -159,3 +159,17 @@ At the end of reflection, ask:
 - Did I identify root causes or just symptoms?
 - Will these changes be maintainable long-term?
 - Am I in the right workflow phase for this reflection focus?
+
+---
+
+## Output Verification
+
+**Before responding, verify your output includes ALL of these:**
+
+- [ ] **Session Summary** - What was accomplished, what went well, friction points
+- [ ] **Effectiveness Analysis** - Token efficiency, context gathering, pattern reuse
+- [ ] **Proposed Changes** - Specific changes with target files and rationale
+- [ ] **Documentation Health** - Line count, bloat assessment, recommendations
+- [ ] **Action Items** - Checklist of concrete next steps
+
+**DO NOT respond until all items are verified.**

package/templates/skills/security-review/SKILL.md

@@ -342,3 +342,18 @@ EOF
 - Trace session lifecycle
 - Review token handling
 - Check for timing vulnerabilities
+
+---
+
+## Output Verification
+
+**Before responding, verify your output includes ALL of these:**
+
+- [ ] **Security Domain** - Identified domains (Auth, API, Admin, Data, Infra)
+- [ ] **Threat Model Summary** - Attack surface, threat actors, attack vectors
+- [ ] **Findings by Severity** - Critical, High, Medium, Low/Informational
+- [ ] **Checklist Status Table** - Passed/Failed/Manual counts per domain
+- [ ] **Verdict** - SECURE, WARNINGS, or ISSUES_FOUND
+- [ ] **GitHub Comment** - Security review posted to issue
+
+**DO NOT respond until all items are verified.**

package/templates/skills/solve/SKILL.md

@@ -194,3 +194,47 @@ If issues depend on each other:
 2. (Wait for PR merge)
 3. /fullsolve 154
 ```
+
+---
+
+## Output Verification
+
+**Before responding, verify your output includes ALL of these:**
+
+- [ ] **Issue Summary Table** - Table with Issue, Title, Labels, Workflow columns
+- [ ] **Recommended Workflow** - Slash commands in order for each issue
+- [ ] **CLI Command** - `sequant run <issue-numbers>` command (REQUIRED)
+- [ ] **Explanation** - Brief notes explaining workflow choices
+
+**DO NOT respond until all items are verified.**
+
+## Output Template
+
+You MUST use this exact structure:
+
+```markdown
+## Solve Workflow for Issues: <ISSUE_NUMBERS>
+
+### Issue Analysis
+
+| Issue | Title | Labels | Workflow |
+|-------|-------|--------|----------|
+<!-- FILL: one row per issue -->
+
+### Recommended Workflow
+
+**For #<N> (<type>):**
+\`\`\`bash
+<!-- FILL: slash commands in order -->
+\`\`\`
+
+### CLI Command
+
+Run from terminal (useful for automation/CI):
+\`\`\`bash
+sequant run <ISSUE_NUMBERS>
+\`\`\`
+
+### Notes
+<!-- FILL: explanation of workflow choices -->
+```

package/templates/skills/spec/SKILL.md

@@ -166,3 +166,62 @@ Post the draft comment to GitHub:
 gh issue comment <issue-number> --body "..."
 gh issue edit <issue-number> --add-label "planned"
 ```
+
+---
+
+## Output Verification
+
+**Before responding, verify your output includes ALL of these:**
+
+- [ ] **AC Checklist** - Numbered AC items (AC-1, AC-2, etc.) with descriptions
+- [ ] **Verification Criteria** - Each AC has Verification Method and Test Scenario
+- [ ] **Implementation Plan** - 3-7 concrete steps with codebase references
+- [ ] **Open Questions** - Any ambiguities with recommended defaults
+- [ ] **Issue Comment Draft** - Formatted for GitHub posting
+
+**DO NOT respond until all items are verified.**
+
+## Output Template
+
+You MUST include these sections in order:
+
+```markdown
+## Acceptance Criteria
+
+### AC-1: [Description]
+
+**Verification Method:** [Unit Test | Integration Test | Browser Test | Manual Test]
+
+**Test Scenario:**
+- Given: [Initial state]
+- When: [Action]
+- Then: [Expected outcome]
+
+### AC-2: [Description]
+<!-- Continue for all AC items -->
+
+---
+
+## Implementation Plan
+
+### Phase 1: [Phase Name]
+1. [Step with specific file/component references]
+2. [Step]
+
+### Phase 2: [Phase Name]
+<!-- Continue for all phases -->
+
+---
+
+## Open Questions
+
+1. **[Question]**
+   - Recommendation: [Default choice]
+   - Impact: [What happens if wrong]
+
+---
+
+--- DRAFT GITHUB ISSUE COMMENT (PLAN) ---
+
+[Complete formatted comment for GitHub]
+```

package/templates/skills/test/SKILL.md

@@ -507,3 +507,17 @@ Testing session is complete when:
 Both can be used together:
 1. `/test` → Verify feature works for users
 2. `/qa` → Verify code quality and completeness
+
+---
+
+## Output Verification
+
+**Before responding, verify your output includes ALL of these:**
+
+- [ ] **Test Summary** - X/Y tests passed
+- [ ] **Test Results Table** - Each test marked PASS, FAIL, or BLOCKED
+- [ ] **Bugs Found** - List of bugs with file:line locations (if any)
+- [ ] **Coverage** - Completed, failed, blocked, remaining counts
+- [ ] **Recommendations** - Next steps for failures or follow-up
+
+**DO NOT respond until all items are verified.**

package/templates/skills/testgen/SKILL.md

@@ -558,3 +558,18 @@ For Issue #452 (hooks):
 ---
 Generated with [Claude Code](https://claude.com/claude-code)
 ```
+
+---
+
+## Output Verification
+
+**Before responding, verify your output includes ALL of these:**
+
+- [ ] **AC Parsing** - Each AC identified with verification method
+- [ ] **Test Stubs Generated** - Files created for Unit/Integration tests
+- [ ] **Browser/Manual Scenarios** - Written for applicable AC items
+- [ ] **Failure Paths** - Error handling stubs for each AC
+- [ ] **Summary Table** - AC count, happy path count, failure path count
+- [ ] **GitHub Comment** - Summary posted to issue
+
+**DO NOT respond until all items are verified.**

package/templates/skills/verify/SKILL.md

@@ -264,3 +264,18 @@ If verification fails due to infrastructure issues:
 4. **File not found:** Verify worktree is correct, check file paths
 
 Report infrastructure issues separately from feature issues.
+
+---
+
+## Output Verification
+
+**Before responding, verify your output includes ALL of these:**
+
+- [ ] **Command Executed** - The exact command that was run
+- [ ] **Exit Code** - Success (0) or error code
+- [ ] **Duration** - How long the command took
+- [ ] **Output Sample** - Captured stdout/stderr (truncated if needed)
+- [ ] **Human Confirmation** - User's verification response recorded
+- [ ] **GitHub Comment** - Verification evidence posted to issue
+
+**DO NOT respond until all items are verified.**