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/adr-template.md

View on GitHub
# ADR Template

General-purpose template for Architecture Decision Records in the VexJoy Agent.
Copy the block below for each new ADR.

---

## File Naming

```
adr/NNN-short-descriptive-slug.md
```

Where `NNN` is the next available number:

```bash
ls adr/ | grep -E '^[0-9]' | sort | tail -1
# then increment by 1
```

Also create `adr/short-descriptive-slug.md` as a one-line redirect to the numbered file.
This satisfies any hooks that look for `adr/{component-name}.md`.

ADR files go in `adr/` (gitignored — they are local development artifacts, not shipped
with the toolkit).

---

## Template

```markdown
# ADR-NNN: [Title]

## Status
Proposed

## Date
YYYY-MM-DD

## Context

[2–4 paragraphs describing the problem. Include:]
- What was found and where — with file:line references for every claim
- Why it matters in practice — concrete scenario, not theoretical risk
- Any relevant system background (architecture, existing behavior, prior ADRs)

[Example of concrete evidence:]

`hooks/userprompt-datetime-inject.py:16` outputs `%H:%M:%S`, which changes every
second. The `additionalContext` field places content in the system prompt prefix —
the cache-sensitive region Claude Code otherwise keeps byte-stable via alphabetical
tool sorting (`src/utils/toolResultStorage.ts`) and content-hash settings paths.
Result: every prompt misses the cache, costing 12.5× more than a cache hit.

## Decision

[Specific implementation plan. Not "improve X" but "replace X with Y in file Z
because reason W".]

[Include before/after code snippets for non-trivial changes:]

```python
# Before (hooks/userprompt-datetime-inject.py:16)
print(f"[datetime] {now.strftime('%Y-%m-%d %H:%M:%S %Z')}")

# After
print(f"[datetime] {now.strftime('%Y-%m-%d %Z')}")
```

[For multi-part decisions, use numbered subsections:]

### 1. [First change]
[Description and code]

### 2. [Second change]
[Description and code]

## Alternatives Considered

### A. [Alternative name]
[Description of the approach]

**Rejected because**: [specific reason — cost, complexity, unavailability, etc.]

### B. [Another alternative]
[Description]

**Deferred because**: [reason — follow-on ADR, future version, etc.]

[Include every alternative that was seriously considered. Showing rejected paths
demonstrates the decision was not arbitrary and prevents future re-litigation.]

## Affected Files

| File | Action | Change |
|------|--------|--------|
| `hooks/your-hook.py` | Create | New hook for [purpose] |
| `.claude/settings.json` | Modify | Register hook in `[EventType]` handlers |

[List every file the implementing agent will touch. Files not listed here will not
be modified. Make the table complete.]

## Consequences

### Positive
- [Concrete improvement with measurable or observable evidence]
- [Another improvement]

### Negative / Risks
- [Tradeoff accepted by this decision]
- [Risk introduced, with mitigation if applicable]

## Implementation Notes

[Specific implementation guidance for the domain agent executing this ADR:]
- [File paths and line numbers]
- [Code patterns to follow or avoid]
- [Sequencing constraints between changes]

**Deploy order for hooks** (per established protocol — deploy file BEFORE registering
in settings.json, or a startup crash will deadlock the session):

1. Create the hook file in the repo
2. Run `python3 hooks/sync-to-user-claude.py` to sync to `~/.claude/hooks/`
3. Verify the hook exits 0 with expected output (see Testing Commands below)
4. Only after verification passes, register in `.claude/settings.json`

## System Integration

[HOW this component plugs into the toolkit. This section is MANDATORY for any ADR
that creates a new component (hook, skill, agent, pipeline). For modification-only
ADRs it may be omitted or shortened.]

### Hook Registration (if applicable)

Add to the appropriate event group in `.claude/settings.json`:

```json
{
  "type": "command",
  "command": "python3 \"$HOME/.claude/hooks/your-hook.py\"",
  "description": "One-line description of what the hook does",
  "timeout": 1000
}
```

[Specify which event type (`UserPromptSubmit`, `PreToolUse`, `PostToolUse`, etc.),
position within the group, and timeout budget.]

### Skill/Agent Registration (if applicable)

Add to `skills/INDEX.json` or `agents/INDEX.json`:

```json
{
  "name": "your-skill",
  "path": "skills/your-skill/SKILL.md",
  "description": "...",
  "triggers": ["trigger phrase", "another phrase"],
  "category": "domain"
}
```

[Include the YAML frontmatter for the new component:]

```yaml
---
name: your-skill
description: "..."
routing:
  triggers:
    - trigger phrase
  category: domain
---
```

### /do Routing (if applicable)

Add to `skills/meta/do/references/routing-tables.md`:

```
| your-skill | trigger phrase, another phrase | domain | description |
```

[Specify triggers, category, and any `pairs_with` entries.]

### Deploy Order

1. [Step with verification gate]
2. [Step with verification gate]
3. Regenerate INDEX: `python3 scripts/generate-skill-index.py` (or agent equivalent)
4. Verify routing: `python3 scripts/routing-benchmark.py --verbose`
5. Register in settings.json (hooks only — after file is deployed and verified)

**CRITICAL**: deploy hook files BEFORE registering in settings.json. Registration of
a broken hook deadlocks every subsequent user prompt.

### Interaction with Other Components

[How this component interacts with existing hooks, skills, agents, or ADRs:]

- **`existing-hook.py`** — [Independent / depends on / must run before/after]
- **ADR-NNN** — [Builds on / supersedes / must be implemented before this]

[If no interactions exist, write "Self-contained — no interactions with existing components."]

### Testing Commands

```bash
# [Describe what this tests]
[exact bash command]

# [Describe what this tests]
[exact bash command]

# Performance check
time [command] <<< '{}'
```

[All commands must be runnable as-is. Include expected output or exit code where
it is not obvious.]

## Router Integration Checklist

[Required for any ADR that creates or modifies a skill, pipeline, or agent.
For hook-only ADRs, write "N/A — no routing changes" and skip this section.]

- [ ] Frontmatter triggers added/updated in component YAML
- [ ] INDEX.json regenerated (`generate-skill-index.py` or `generate-agent-index.py`)
- [ ] Entry added to `skills/meta/do/references/routing-tables.md`
- [ ] Trigger collision check passed (no duplicate triggers across force-routed entries)
- [ ] Pipeline companion map updated (if component pairs with existing pipelines)
- [ ] Quick-reference examples added to routing tables
- [ ] `python3 scripts/routing-benchmark.py --verbose` passes

## Validation Requirements

[What must be demonstrably true before this ADR is considered implemented:]

1. [Specific, runnable verification — exact command with expected output]
2. [Another verification]
3. [Performance check if applicable — e.g., execution time under 50ms]
4. [Edge case — malformed input, missing env var, etc.]

[These requirements become the PR acceptance criteria. Write them so that a domain
agent can execute them mechanically and report pass/fail.]

## References

- [`path/to/file.py`] — [What this file is and why it is relevant]
- [ADR-NNN] — [What that ADR decided and how it relates]
- [`research/topic.md`] — [What the research found]
```

---

## Notes for ADR Writers

**Context must cite file:line.** Every claim about code behavior needs a location.
"The hook outputs the wrong format" is not verifiable. "The hook outputs `%H:%M:%S`
at `hooks/userprompt-datetime-inject.py:16`" is verifiable.

**Decision must be implementable by a domain agent.** The agent reads the Decision
section and executes it. "Improve error handling" is not implementable. "Replace bare
`except:` on line 47 of `hooks/foo.py` with `except (json.JSONDecodeError, OSError) as e:`
and log the error to stderr" is implementable.

**Alternatives Considered is not optional.** Every seriously-considered path that was
not taken should appear here with a reason. This prevents relitigating the decision
later and shows the operator the decision was not arbitrary.

**System Integration is MANDATORY for new components.** Any ADR that creates a hook,
skill, agent, or pipeline must include the System Integration section with all
applicable subsections filled in. Skipping it produces a component that exists on disk
but is invisible to `/do` and not registered in settings.json.

**Router Integration Checklist is MANDATORY for new routable components.** Any ADR
creating a skill, agent, or pipeline must complete all checklist items before the PR
merges. A routable component without routing table entries is effectively invisible
to the toolkit.

**Sections marked "(if applicable)" can be removed entirely.** If this ADR creates
no hooks, delete the Hook Registration subsection. If it creates no skills, delete
Skill/Agent Registration. Do not leave empty subsections with placeholder text.

**The Affected Files table is the implementing agent's scope boundary.** The agent
only touches files listed there. If a file is missing from the table, the agent will
not modify it. Make the table complete before approving the ADR for implementation.

**Keep the Execution Plan optional.** For most ADRs, the Implementation Notes and
Affected Files table are sufficient. An elaborate 7-phase Execution Plan with parallel
worktrees and validation gates is only warranted for ADRs that create multiple
interdependent new components. If the change is a one-line fix, the Implementation
Notes section is enough.
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