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/pl-executor-ready-plan-template.md

View on GitHub
# Executor-Ready Plan Template

Plans consumed by subagent executors (via `subagent-driven-development`) must be self-contained. An executor runs in a fresh context with no memory of the planning session. Everything the executor needs — code excerpts, file paths, verification commands, stop conditions — must be inline in the plan. "See file X" is not a plan step; it is a token-burning detour.

"Executor" here is SDD's implementer subagent; the two terms name the same role.

When loaded alongside `plan-files.md`: for SDD-executed plans this skeleton replaces the plan-files skeleton. Keep plan-files' Status line for resumability; the other plan-files sections (Phases, Key Questions) are covered by Steps and STOP Conditions here.

---

## Plan Structure

Every executor-ready plan follows this skeleton. Sections marked **(required)** cause executor failure when absent.

````markdown
# Plan: [Title]

## Metadata (required)
- **Created**: YYYY-MM-DD
- **Base SHA**: [output of `git rev-parse --short HEAD` at plan creation time]
- **Branch**: [branch name]
- **Author**: [who created the plan]

## Goal (required)
[One sentence: the end state this plan produces.]

## Scope (required)

### In-scope files
[Exhaustive list of files this plan creates or modifies. One per line.]
- `path/to/file-a.go`
- `path/to/file-b.go`

### Out-of-scope files
[Files the executor must leave untouched. Touching these triggers a STOP.]
- `path/to/unrelated.go`
- `config/production.yaml`

## Steps (required)

### Step 1: [Title]

**What**: [Concrete description of the change.]

**Context** (inlined):
```[language]
// Current state of the code being changed.
// Paste the relevant excerpt here — 10-30 lines, enough to act on.
// The executor reads this, not the file.
```

**Do**:
1. [Specific instruction]
2. [Specific instruction]

**Verify**:
```bash
[command that confirms this step succeeded]
```
**Expected output**: [exact string, pattern, or exit code]

---

### Step N: [Title]
[Same structure as Step 1]

## STOP Conditions (required)

Executor must STOP and escalate (report status, request human decision) when
any of these triggers fire:

1. **Drift detected**: the Base SHA in Metadata is no longer an ancestor of
   HEAD (`git merge-base --is-ancestor <base-sha> HEAD` fails), or a step's
   Context excerpt no longer matches the current file content. Commits made by
   the plan's own earlier steps move HEAD forward and are NOT drift; a rebase,
   reset, branch switch, or edited excerpt means the plan's assumptions may be
   stale.
2. **Verification fails twice**: A step's verify command fails, the executor
   retries once, and it fails again. Two failures signal a plan defect, not a
   transient error.
3. **Out-of-scope touch required**: Completing a step requires modifying a file
   listed in "Out-of-scope files." The plan's boundary was drawn wrong; a human
   must decide whether to expand scope.
4. **Ambiguous or missing instruction**: A step's "Do" section is unclear
   enough that two reasonable interpretations exist, or a section marked
   (required) is absent from the plan. Guessing risks rework.
5. **Test regression**: A previously passing test fails after a step. The change
   broke something outside the step's intent.

## Completion Criteria (required)
[How to verify the entire plan succeeded — final command + expected output.]
````

---

## Drift Check Protocol

The Base SHA is the plan's anchor to a specific codebase state. Every code excerpt, file path, and verification command assumes that state.

**Plan author** stamps the SHA at plan creation:
```bash
git rev-parse --short HEAD
```

**Executor** verifies before starting each dispatch:
```bash
if ! git merge-base --is-ancestor <base-sha> HEAD; then
  echo "DRIFT DETECTED: base <base-sha> is not an ancestor of HEAD"
  echo "STOP: plan assumptions may be stale"
  exit 1
fi
```

The check is an ancestry test, not an equality test, because SDD runs plans as a per-task loop: each task commits and moves HEAD forward, so only the first dispatch can expect HEAD to equal the Base SHA. Commits produced by the plan's own earlier steps keep the Base SHA an ancestor and are not drift. Before editing a file, the executor also confirms the step's inlined Context excerpt still matches the file; a mismatch is drift even when ancestry holds.

If either check fails: STOP. Report the mismatch. The planner must update the plan against the current state or confirm the plan still applies.

---

## Per-Step Verification Rules

Every step ends with a verify block. The verify block is a contract: if the command produces the expected output, the step succeeded. If not, the step failed.

**Good verification** (deterministic, specific):
````markdown
**Verify**:
```bash
go test ./auth/... -run TestTokenRefresh -count=1
```
**Expected output**: `ok  auth  0.XXXs` (exit code 0)
````

**Bad verification** (vague, untestable):
```markdown
**Verify**: "Check that the code looks correct"
```

Rules:
1. Every verify command must be runnable without human judgment.
2. Expected output must be specific enough to distinguish pass from fail.
3. Prefer exit codes and grep-able strings over visual inspection.
4. When no command can verify the step (pure refactor with no behavioral change), use: `git diff --stat` + expected file list.

---

## Inlining Context

Executor subagents run in fresh context. File references ("see `auth/token.go` lines 45-60") cost the executor a Read tool call, token budget, and risk reading stale content if another step modified the file.

**Inline instead**:
- Paste 10-30 lines of the relevant code excerpt directly in the step's Context block.
- Include enough surrounding context (function signature, imports) for the executor to orient.
- Mark the excerpt's source: `// from auth/token.go:45-60 at base SHA abc1234`.

**When NOT to inline**:
- File is > 100 lines and the entire file is relevant: reference the file path but note "read this file in full before starting this step."
- File will be created from scratch: provide the full intended content in the "Do" section instead.

---

## Scope Boundaries

Explicit scope prevents executor drift — the most common failure mode in multi-step plans.

**In-scope files**: Every file the plan touches. The executor treats this as a whitelist. Creating or modifying a file absent from this list is a scope violation.

**Out-of-scope files**: Files related to the work but intentionally excluded. Naming them prevents the executor from "helpfully" fixing adjacent issues.

**Why both lists**: In-scope alone leaves a gray area — is an unlisted file fair game or forbidden? The out-of-scope list removes ambiguity. Together they form a complete boundary.

---

## Integration with Subagent-Driven Development

SDD's executor loop (Phase 2) consumes plans in this format. The plan's Base SHA (stamped at plan creation, anchors drift detection) is distinct from SDD's `{BASE_SHA}` (captured at execution start, anchors the final integration-review diff); do not conflate them. The contract:

1. **Drift check**: Executor runs the ancestry drift check from Metadata before touching any file, and confirms each step's Context excerpt before editing. Failure triggers STOP condition 1.
2. **Step-by-step execution**: Executor follows steps in order, running each verify block before proceeding. Failure triggers STOP condition 2.
3. **Scope enforcement**: Executor checks every file it modifies against the in-scope list. Out-of-scope touch triggers STOP condition 3.
4. **Escalation path**: On any STOP, the executor reports what it completed, what triggered the stop, and what decision it needs. It waits for human direction rather than improvising.

The planner's job is to make the executor's job mechanical. If the executor needs judgment, the plan is underspecified.
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