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/mcp-pipeline-builder/references/design-rules.md

View on GitHub
# Phase 2 Design Rules

Rules for converting `analysis.md` into `design.md`. Follow these in order.

---

## Primitive Selection

Use this heuristic table for every operation in the analysis. When in doubt, use a Tool — Tools are always acceptable; Resources and Prompts are optional specializations.

| If the operation... | Expose as... | Reason |
|--------------------|-------------|--------|
| Requires parameters to identify what to fetch | **Tool** | Parameters need schema validation and error handling |
| Has side effects (creates, updates, deletes) | **Tool** (or excluded) | Side effects require explicit invocation |
| Has complex validation or business logic | **Tool** | Tools handle validation; resources don't |
| Is a CLI command | **Tool** | Commands have flags/args that map to parameters |
| Is a REST endpoint | **Tool** | Endpoints map cleanly to tool call/response |
| Is stable, URI-addressable reference data | **Resource** | Schema files, config templates, docs pages |
| Is a canned workflow prompt | **Prompt** | Only expose if clearly high-value and reusable |
| Is authentication configuration | Neither (env var in README) | Not an operation; handled at server startup |

**Practical rule**: When in doubt, use a Tool. Resources are for genuinely static or template-URI-addressable data (e.g., `schema://users`, `docs://authentication`). Prompts are rarely needed.

---

## Tool Naming Convention

Format: `{service}_{verb}_{noun}` — all lowercase, underscores as separators.

| Component | Rules |
|-----------|-------|
| `{service}` | Short name of the target service (1–2 words max). Examples: `github`, `jira`, `kubectl`, `pg` |
| `{verb}` | Action word. Prefer: `get`, `list`, `search`, `create`, `update`, `delete`. Reserve `fetch`, `retrieve`, and `obtain` for cases where those verbs are already part of the target API |
| `{noun}` | Primary entity being operated on. Use singular for single-entity ops, plural for list ops |

**Examples**:
- `github_get_issue` — get a single issue by number
- `github_list_issues` — list issues with filters
- `github_get_issue_with_comments` — merged tool (issue + its comments together)
- `jira_search_issues` — JQL search
- `kubectl_get_pod_logs` — get logs for a specific pod
- `pg_execute_query` — execute a read-only SQL query

**Anti-examples**:
- `fetchIssue` — wrong case, wrong separator
- `get_github_data` — too vague, doesn't name the entity
- `github_retrieve_an_issue_by_its_number` — verbose, not idiomatic

---

## Workflow-Tool vs API-Wrapper Rule

**The most important design decision in Phase 2.**

An MCP server with 30 narrow tools is worse than one with 10 workflow tools. When a model uses the server, it must select the right tool. Many similar tools create decision paralysis and waste tool-call turns.

### The Test

Ask for each pair of operations: "Would a user ever call operation A without also wanting the result of operation B?"

- If **usually no** → merge into one tool
- If **sometimes no** → consider merging; add the secondary data as an optional field

### Common Merges

| Separate (wrong) | Merged (right) | Reasoning |
|-----------------|----------------|-----------|
| `github_get_issue` + `github_get_issue_comments` | `github_get_issue_with_context` | Reading an issue without its comments rarely serves a purpose |
| `kubectl_get_pod` + `kubectl_get_pod_logs` | `kubectl_get_pod_status` (returns pod + recent logs) | Debugging pods always needs both |
| `jira_get_issue` + `jira_get_issue_transitions` | `jira_get_issue_with_workflow` | Workflow state is always relevant when viewing an issue |

### Granularity Target

| Tool count | Assessment |
|------------|-----------|
| 3–5 | Acceptable for narrow services; check you haven't over-merged |
| 5–15 | Ideal range. Tools are specific but not overlapping |
| 15–20 | Warning zone. Review for merging opportunities |
| > 20 | Stop. Group before proceeding. Return to grouping step |

---

## Destructive Tool Handling

By default (no `--allow-destructive` flag):
1. Read every write operation from `analysis.md` → Write Operations section
2. Leave destructive operations out of `design.md` by default
3. Add a single `design.md` section: "Excluded Operations" listing what was dropped and why

If `--allow-destructive` is set:
1. Include write operations as tools
2. Mark each with `annotations: { destructiveHint: true, idempotentHint: false }`
3. Write an explicit warning in `design.md`: "These tools modify data. Review carefully."
4. Still ask for user confirmation at the Phase 2 gate about the destructive tools specifically

---

## Transport Selection Rules

| If... | Then transport = |
|-------|----------------|
| Target is a local CLI tool or library | stdio |
| Target's README describes a base URL to call | HTTP |
| Target repo has an Express/FastAPI/Django server as its main component | HTTP |
| Target repo IS the server you're calling | HTTP |
| Uncertain | stdio (safer default; can always add HTTP later) |

Record the transport decision and its reason in `design.md`.

---

## Parameter Schema Guidance

For each tool, specify parameters with this precision:

```
name: {param_name}
  type: string | number | boolean | array | object
  required: yes | no
  description: {what this controls, in plain language}
  example: {a realistic example value}
```

**Required vs optional**:
- Required: parameters needed to identify the target resource (e.g., `owner`, `repo`, `issue_number`)
- Optional: filters, pagination, format preferences (e.g., `state: "open"`, `limit: 20`)

**Type choices**:
- Prefer `string` for identifiers, even numeric-looking ones (e.g., issue numbers → string for flexibility)
- Use `number` for quantities and numeric comparisons
- Use `boolean` for flags (e.g., `include_comments: true`)
- Prefer flat top-level parameters; use individual fields instead of `object`

**Description format**:
- One sentence, plain language
- Include valid values if constrained: `"Filter by state. One of: open, closed, all"`
- Include units for numeric params: `"Maximum number of results to return. Default: 20, max: 100"`

---

## Output Format for `design.md`

```markdown
# MCP Server Design: {Server Name}

## Target Service
{service name and one-line description from analysis.md}

## Configuration
- Target language: TypeScript | Python
- Transport: stdio | HTTP
- Server name (slug): {service}-mcp-server
- Auth: {how the server will read credentials}

## Tools

### {tool_name}
**Description**: {2–3 sentences: what this does, for what use case, what it returns}

**Parameters**:
| Name | Type | Required | Description |
|------|------|----------|-------------|
| {param} | {type} | yes/no | {description} |

**Response**: {describe the structure of the successful response}

**Annotations**:
- readOnlyHint: true | false
- destructiveHint: true | false
- idempotentHint: true | false

---

{repeat for each tool}

## Resources (if any)

### {resource_uri_template}
**Description**: {what this resource contains}
**MIME type**: {text/plain | application/json | text/markdown}

## Excluded Operations
{List of write operations excluded because --allow-destructive was not set}

## Notes
{Any design decisions, trade-offs, or warnings for the user to review}
```
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