Skip to content

notque/vexjoy-agent / skills/process/workflow

workflow

Verified

Structured work: multi-phase tasks, feature builds, planning, objective loops, hill climbing.

FileKindSize
SKILL.mdskill md13.2 KB
references/adr-template.mdmarkdown9.4 KB
references/agent-upgrade.mdmarkdown12.5 KB
references/article-evaluation-pipeline.mdmarkdown8.9 KB
references/article-evaluation-pipeline/references/report-template.mdmarkdown2.5 KB
references/article-evaluation-pipeline/references/wabi-sabi-classification.mdmarkdown2.4 KB
references/auto-pipeline.mdmarkdown12.5 KB
references/auto-pipeline/references/pipeline-catalog.jsonconfig15.0 KB
references/auto-pipeline/references/pipeline-catalog.mdmarkdown4.3 KB
references/build_dag.pyscript12.5 KB
references/chain-composer.mdmarkdown20.4 KB
references/chain-composer/references/canonical-chains.mdmarkdown13.9 KB
references/comprehensive-review-workflow.jsscript19.3 KB
references/comprehensive-review.mdmarkdown27.8 KB
references/comprehensive-review/references/output-templates.mdmarkdown10.6 KB
references/comprehensive-review/references/wave-0-per-package.mdmarkdown5.6 KB
references/comprehensive-review/references/wave-1-foundation.mdmarkdown10.4 KB
references/comprehensive-review/references/wave-2-deep-dive.mdmarkdown7.3 KB
references/comprehensive-review/references/wave-3-adversarial.mdmarkdown7.4 KB
references/dag-compatibility-matrix.mdmarkdown13.0 KB
references/dag-composition-patterns.mdmarkdown5.0 KB
references/dag-orchestration-advanced.mdmarkdown6.3 KB
references/dag-orchestration-examples.mdmarkdown11.4 KB
references/dag-skill-patterns.mdmarkdown12.5 KB
references/de-ai-pipeline.jsscript14.6 KB
references/de-ai-pipeline.mdmarkdown6.3 KB
references/discover_skills.pyscript12.1 KB
references/do-perspectives.mdmarkdown11.5 KB
references/doc-pipeline.mdmarkdown9.2 KB
references/domain-research.mdmarkdown32.8 KB
references/domain-research/references/task-type-guide.mdmarkdown11.4 KB
references/explore-pipeline.jsscript18.6 KB
references/explore-pipeline.mdmarkdown15.0 KB
references/fan-out-workflow.jsscript9.7 KB
references/fan-out-workflow.pyscript10.4 KB
references/feedback-loop-construction.mdmarkdown14.3 KB
references/fl-design.mdmarkdown9.6 KB
references/fl-error-handling.mdmarkdown8.5 KB
references/fl-implement.mdmarkdown7.6 KB
references/fl-pipeline.mdmarkdown6.0 KB
references/fl-plan.mdmarkdown11.0 KB
references/fl-release.mdmarkdown3.8 KB
references/fl-shared.mdmarkdown3.6 KB
references/fl-validate.mdmarkdown4.5 KB
references/github-profile-rules.mdmarkdown10.5 KB
references/github-profile-rules/references/rule-categories.mdmarkdown6.5 KB
references/hc-SPEC.mdmarkdown3.3 KB
references/hc-domain-playbooks.mdmarkdown15.4 KB
references/hc-ledger.mdmarkdown3.3 KB
references/hc-profiling-tools.mdmarkdown3.7 KB
references/hill-climb.mdmarkdown9.3 KB
references/hook-development-pipeline.mdmarkdown12.9 KB
references/mcp-pipeline-builder.mdmarkdown16.3 KB
references/mcp-pipeline-builder/references/analysis-checklist.mdmarkdown6.2 KB
references/mcp-pipeline-builder/references/design-rules.mdmarkdown7.1 KB
references/mcp-pipeline-builder/references/evaluation-guide.mdmarkdown7.6 KB
references/mcp-pipeline-builder/references/python-scaffold-template.mdmarkdown9.5 KB
references/mcp-pipeline-builder/references/ts-scaffold-template.mdmarkdown1.6 KB
references/mcp-pipeline-builder/scripts/assemble-scaffold.pyscript6.3 KB
references/mcp-pipeline-builder/scripts/register_mcp.pyscript6.9 KB
references/mcp-pipeline-builder/templates/client-cli.ts.tmplother682 B
references/mcp-pipeline-builder/templates/client-http.ts.tmplother1.4 KB
references/mcp-pipeline-builder/templates/index.ts.tmplother1.1 KB
references/mcp-pipeline-builder/templates/package.json.tmplother477 B
references/mcp-pipeline-builder/templates/readme.md.tmplother1.1 KB
references/mcp-pipeline-builder/templates/tools.ts.tmplother3.0 KB
references/mcp-pipeline-builder/templates/ts-scaffold.tmplother556 B
references/mcp-pipeline-builder/templates/tsconfig.json.tmplother408 B
references/ol-SPEC.mdmarkdown2.4 KB
references/ol-state-file.mdmarkdown2.9 KB
references/pipeline-index.jsonconfig23.9 KB
references/pipeline-orchestrator.mdmarkdown15.3 KB
references/pipeline-orchestrator/orchestration-patterns.mdmarkdown8.1 KB
references/pipeline-orchestrator/preferred-patterns.mdmarkdown4.6 KB
references/pipeline-retro.mdmarkdown19.0 KB
references/pipeline-scaffolder.mdmarkdown22.4 KB
references/pipeline-scaffolder/references/architecture-rules.mdmarkdown18.9 KB
references/pipeline-scaffolder/references/generated-skill-template.mdmarkdown1.9 KB
references/pipeline-scaffolder/references/pipeline-spec-format.mdmarkdown36.8 KB
references/pipeline-scaffolder/references/step-menu.mdmarkdown21.5 KB
references/pipeline-scaffolder/scripts/assemble-skill.pyscript6.3 KB
references/pipeline-scaffolder/templates/phases/decision-planning.md.tmplother1.2 KB
references/pipeline-scaffolder/templates/phases/domain-extension.md.tmplother1.5 KB
references/pipeline-scaffolder/templates/phases/generation.md.tmplother427 B
references/pipeline-scaffolder/templates/phases/git-release.md.tmplother1.1 KB
references/pipeline-scaffolder/templates/phases/interaction.md.tmplother965 B
references/pipeline-scaffolder/templates/phases/learning-retro.md.tmplother1.5 KB
references/pipeline-scaffolder/templates/phases/observation.md.tmplother1.3 KB
references/pipeline-scaffolder/templates/phases/research-gathering.md.tmplother1.2 KB
references/pipeline-scaffolder/templates/phases/review.md.tmplother930 B
references/pipeline-scaffolder/templates/phases/safety-guarding.md.tmplother1.7 KB
references/pipeline-scaffolder/templates/phases/structuring.md.tmplother361 B
references/pipeline-scaffolder/templates/phases/synthesis-reporting.md.tmplother1.9 KB
references/pipeline-scaffolder/templates/phases/validation.md.tmplother1.1 KB
references/pipeline-scaffolder/templates/skill-template.md.tmplother12.0 KB
references/pipeline-test-runner.mdmarkdown16.7 KB
references/pl-ambiguity-triage.mdmarkdown2.7 KB
references/pl-check-dimensions.mdmarkdown7.4 KB
references/pl-check-errors.mdmarkdown824 B
references/pl-check-verdict-format.mdmarkdown3.2 KB
references/pl-check.mdmarkdown6.5 KB
references/pl-context-boundary.mdmarkdown1.6 KB
references/pl-depth-first-interview.mdmarkdown11.6 KB
references/pl-empirical-prototype.mdmarkdown825 B
references/pl-executor-ready-plan-template.mdmarkdown7.7 KB
references/pl-human-source-elicitation.mdmarkdown1.5 KB
references/pl-manage.mdmarkdown5.1 KB
references/pl-pause-confirm-and-errors.mdmarkdown2.1 KB
references/pl-pause-extract-decisions.mdmarkdown3.0 KB
references/pl-pause-gather-steps.mdmarkdown2.3 KB
references/pl-pause-synthesize-fields.mdmarkdown2.3 KB
references/pl-pause-write-templates.mdmarkdown5.3 KB
references/pl-pause.mdmarkdown6.5 KB
references/pl-plan-files.mdmarkdown8.4 KB
references/pl-pre-plan.mdmarkdown11.6 KB
references/pl-resume.mdmarkdown12.3 KB
references/pl-spec.mdmarkdown5.2 KB
references/pr-fix-loop.mdmarkdown10.3 KB
references/pr-fix-loop/references/message-formats.mdmarkdown1.6 KB
references/pr-fix-loop/references/publish.mdmarkdown5.4 KB
references/pr-fix-loop/references/review-checklist.mdmarkdown3.4 KB
references/pr-pipeline/references/pr-templates.mdmarkdown5.4 KB
references/pr-pipeline/references/preflight-checklist.mdmarkdown2.8 KB
references/pr-pipeline/references/retro-adr-phases.mdmarkdown2.7 KB
references/pr-pipeline/references/review-fix-loop.mdmarkdown2.0 KB
references/project-coordinator.mdmarkdown6.5 KB
references/project-coordinator/agent-capability-map.mdmarkdown5.4 KB
references/project-coordinator/communication-protocols.mdmarkdown4.5 KB
references/project-coordinator/coordination-playbook.mdmarkdown3.7 KB
references/project-coordinator/death-loop-prevention.mdmarkdown3.6 KB
references/project-coordinator/error-catalog.mdmarkdown2.7 KB
references/project-coordinator/parallel-execution-patterns.mdmarkdown2.8 KB
references/project-coordinator/preferred-patterns.mdmarkdown5.9 KB
references/project-coordinator/todowrite-integration.mdmarkdown5.6 KB
references/research-pipeline.jsscript15.2 KB
references/skill-creation-pipeline.mdmarkdown17.1 KB
references/system-upgrade.mdmarkdown12.8 KB
references/systematic-debugging.mdmarkdown11.0 KB
references/systematic-refactoring.mdmarkdown11.4 KB
references/toolkit-improvement.jsscript39.0 KB
references/toolkit-improvement.mdmarkdown20.5 KB
references/toolkit-improvement/references/adr-template.mdmarkdown10.5 KB
references/toolkit-improvement/references/agent-roster.mdmarkdown15.8 KB
references/workflow-helpers.jsscript12.1 KB
references/workflow-orchestrator.mdmarkdown20.8 KB
references/workflow-orchestrator/references/plan-template.mdmarkdown1.3 KB
references/workflow-orchestrator/references/task-patterns.mdmarkdown23.3 KB
references/workflow-orchestrator/scripts/assemble-plan.pyscript6.9 KB
references/workflow-orchestrator/scripts/validate.pyscript14.4 KB
references/workflow-orchestrator/templates/plan-template.json.tmplother904 B

references/fl-error-handling.md

View on GitHub
# Error Handling Reference

> **Scope**: Recovery patterns for feature-state.py CLI failures, phase transition errors, artifact issues, and agent dispatch failures within the feature lifecycle skill.
> **Version range**: all versions
> **Generated**: 2026-04-17

---

## Overview

The feature lifecycle skill uses `feature-state.py` as the single source of truth for phase tracking. Most errors fall into four categories: phase mismatches (requesting a phase the state machine isn't ready for), missing artifacts (previous phase didn't complete), agent dispatch failures (task agents returning errors), and gate failures (quality criteria not met). Each has a distinct recovery path — routing to the wrong path wastes entire waves of work.

---

## Pattern Table

| Situation | Correct Recovery | Wrong Recovery |
|-----------|-----------------|----------------|
| Phase mismatch | Report current phase, suggest correct next | Silently advance state |
| Missing artifact | Route back to producing phase | Proceed with empty artifact |
| Agent dispatch fails x3 | Stop, report to user | Retry indefinitely |
| Gate failure | Report exactly what failed, stop | Approve and advance |
| Tier 3 architectural deviation | Stop, present options | Auto-apply and continue |

---

## Correct Patterns

### Always Check State Before Acting

Check the feature state machine before dispatching any work in a phase.

```bash
# Verify phase is what you expect before loading anything
python3 ~/.claude/scripts/feature-state.py status my-feature
```

**Why**: The user may have partially completed a prior run, abandoned a phase, or the state file may reflect a different feature than the session context. Acting on stale assumptions causes cascading plan-vs-reality drift across waves.

---

### Record Gate Failures Before Stopping

When a gate fails, record the failure before stopping so retries start with context.

```bash
# Record the gate failure
python3 ~/.claude/scripts/feature-state.py gate my-feature validate.test-failure

# Document what failed
python3 ~/.claude/scripts/feature-state.py retro-record my-feature gate-failure \
  "validate: 3 tests failed in auth module" --confidence high
```

**Why**: Gate failures without records force re-diagnosis on retry. The retro system surfaces these as patterns so the plan phase can allocate more time to high-failure areas.

---

### Tier Classification Before Acting on Deviations

Classify every deviation before choosing a recovery path.

```bash
# After classifying as Tier 3 — stop and present to user
python3 ~/.claude/scripts/feature-state.py gate my-feature implement.architectural-deviation
```

```
Tier 1 (auto-fix):  bug, import error, type error → apply fix, record in retro, continue
Tier 2 (blocking):  missing dep, config issue → attempt auto-fix, record, escalate if stuck
Tier 3 (arch):      schema change, API redesign, scope expansion → STOP, present to user
```

**Why**: Tier 3 deviations represent scope changes the plan didn't authorize. Auto-applying them hides architectural decisions in implementation output where they can't be reviewed.

---

## Pattern Catalog

### Check Feature State Before Every Action

**Detection**:
```bash
# Look for advance calls without a preceding status check in the same block
grep -n 'feature-state.py advance' skills/process/workflow/references/fl-*.md
rg 'feature-state\.py (checkpoint|advance)' skills/
```

**Signal**:
```bash
# Missing: python3 ~/.claude/scripts/feature-state.py status my-feature
python3 ~/.claude/scripts/feature-state.py advance my-feature
```

**Why this matters**: Advancing without reading state can skip a phase or double-advance when a prior partial run already moved the state forward. The state file is authoritative; skipping the read assumes it matches session context.

**Preferred action**:
```bash
python3 ~/.claude/scripts/feature-state.py status my-feature
# Only if output confirms phase is ready:
python3 ~/.claude/scripts/feature-state.py advance my-feature
```

---

### Stop and Report After Three Agent Failures

**Detection**:
```bash
grep -rn 'Attempt [4-9]\|Attempt [0-9][0-9]' .feature/state/implement/
rg 'retry.*attempt|attempt.*[4-9]' .feature/ --ignore-case
```

**Signal**:
```
Attempt 1: Agent dispatch failed (no output)
Attempt 2: Agent dispatch failed (timeout)
Attempt 3: Agent dispatch failed (malformed response)
Attempt 4: Retrying with more context...  ← wrong
```

**Why this matters**: Three consecutive failures signal a structural problem: wrong agent type, missing prerequisite context, or a malformed task spec. More retries don't fix structural problems — they burn budget while delaying root-cause diagnosis.

**Preferred action**: After three failures, stop and report:
```
Task [name] failed 3 times. Root cause candidates:
- Agent type mismatch (assigned: X, task domain: Y)
- Missing prerequisite context (wave N depended on wave N-1 artifact)
- Task spec too ambiguous (file list or operations underspecified)

Blocked. Requires user input to continue.
```

---

### Block Advancement on Gate Failure

**Detection**:
```bash
grep -rn 'gate.*fail\|BLOCKED.*proceed\|proceeding.*fail' .feature/state/ --ignore-case
rg 'minor failure|appears minor|otherwise complete' .feature/
```

**Signal**:
```
Gate: Validate failed (2 tests failing), but proceeding to release because
      failures appear minor and the feature is otherwise complete.
```

**Why this matters**: Gates are binary. Downstream phases depend on upstream correctness — releasing with failing validation tests ships broken code. There is no "minor failure" category.

**Preferred action**:
```
Gate failed: validate (2 tests failing)
  - auth_test.go:TestLoginExpiry
  - auth_test.go:TestRefreshToken
BLOCKED. Cannot advance to release. Fix failing tests and re-run validate.
```

---

### Use the CLI for All State Mutations

**Detection**:
```bash
# Find scripts opening the state JSON directly instead of via CLI
rg '\.feature/state.*\.json' . --type py
grep -rn 'open.*feature.*state' . --include="*.py"
```

**Signal**:
```python
import json
with open('.feature/state/my-feature.json', 'w') as f:
    json.dump({'phase': 'validate', ...}, f)  # direct write — wrong
```

**Why this matters**: The state file format is an implementation detail of `feature-state.py`. Direct writes bypass validation, lock acquisition, and event recording. The CLI is the contract; the file schema is not.

**Preferred action**:
```bash
# Always use the CLI, never the file path
python3 ~/.claude/scripts/feature-state.py advance my-feature
python3 ~/.claude/scripts/feature-state.py gate my-feature implement.custom-gate
```

---

## Error-Fix Mappings

| Error Message | Root Cause | Fix |
|---------------|------------|-----|
| `Phase mismatch: expected implement, current is plan` | Advance called before plan phase completed | Complete plan phase, run `checkpoint plan`, then advance |
| `No design artifact found in .feature/state/design/` | Design phase did not write artifact, or wrong slug | Re-run design phase; verify feature name slug matches directory |
| `Consultation required for Medium+ feature` | ADR exists but no synthesis.md | Run `/adr-consultation` before continuing implement |
| `Consultation blocked implementation` | synthesis.md verdict is BLOCKED | Resolve concerns in `adr/{name}/concerns.md`, then re-consult |
| `Gate already passed: {name}` | Gate command called twice (idempotent) | Safe to ignore — gate was recorded on first call |
| `Feature not found: {slug}` | Slug doesn't match initialized feature | Run `feature-state.py status` to list active features |
| `Cannot advance: current phase has no completion checkpoint` | Checkpoint not recorded before advance | Run `checkpoint {phase}` with artifact, then advance |

---

## Detection Commands Reference

```bash
# Find state advance calls in lifecycle refs
rg 'feature-state\.py advance' skills/process/workflow/references/ -g 'fl-*.md'

# Find gate failures in feature logs
grep -rn 'Gate.*fail\|BLOCKED' .feature/state/

# Find direct state file manipulation (bypass anti-pattern)
rg '\.feature/state.*\.json' . --type py

# Find agent retry loops beyond threshold in implement logs
grep -c 'Attempt' .feature/state/implement/*.md 2>/dev/null

# Confirm all phase artifacts exist before release
ls .feature/state/design/ .feature/state/plan/ .feature/state/implement/ .feature/state/validate/
```

---

## See Also

- `shared.md` — state machine commands and directory structure
- `implement.md` — Tier 1/2/3 deviation classification detail
- `validate.md` — gate definitions and quality gate skill routing
planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies.Stars: 108kUpdated Claude CodeCodexVerifiedInstall
meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要".Stars: 108kUpdated Claude CodeCodexVerifiedInstall