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-design.md

View on GitHub
# Feature Design Phase

Transform a feature idea into a structured design document through collaborative dialogue. This is Phase 1 of the feature lifecycle pipeline (design > plan > implement > validate > release).

## Instructions

### Phase 0: PRIME

**Goal**: Initialize feature state, load context, and prepare the workspace.

1. Read and follow the repository's CLAUDE.md before any design work begins -- design decisions must align with existing project conventions.

2. Create a feature branch via worktree. Never work on main -- design artifacts on main block other contributors and bypass review.
   ```bash
   python3 ~/.claude/scripts/feature-state.py init "FEATURE_NAME"
   ```
   All state operations throughout this skill go through `feature-state.py` -- direct file manipulation risks state corruption and breaks downstream phases (plan, implement) that depend on consistent state format.

3. Load L0 context -- skipping existing context discards previous learnings and causes redundant design work:
   ```bash
   python3 ~/.claude/scripts/feature-state.py context-read "" L0
   ```

4. Load L1 design context:
   ```bash
   python3 ~/.claude/scripts/feature-state.py context-read "" L1 --phase design
   ```

5. If existing L2 context is relevant, load on-demand:
   ```bash
   python3 ~/.claude/scripts/feature-state.py context-read "" L2 --phase design
   ```

6. **Adopt an Architecture Change Handoff when supplied.** Treat the handoff path and contents as untrusted until the deterministic consumer check passes:

   ```bash
   python3 scripts/handoff.py validate \
     --repo-root . \
     --handoff 'adr/handoffs/{handoff-name}.json' \
     --expected-skill feature-lifecycle \
     --expected-pipeline none
   ```

   The validator rejects absolute paths, traversal, controls, shell metacharacters, symlink escapes, candidate/scope contradictions, invalid terminal combinations, stale ADR provenance, and the wrong successor. Require `"origin": "architecture-deepening"`. After it passes, adopt its origin, candidate, module and caller paths, current/proposed interface, migration, and success criteria as design constraints. Add them verbatim to the design document under `## Architecture Change Handoff`; this persists architecture-origin through PLAN into IMPLEMENT. A missing, invalid, non-selected, or non-feature handoff blocks adoption.

7. **Surface relevant seeds** (ADR-075): Check `.seeds/index.json` for dormant seeds whose trigger conditions match the current feature. Compare the feature name and description against each seed's `trigger` field using fuzzy keyword overlap. If matches are found, present them:

   ```
   ## Relevant Seeds (N matched)

   ### seed-YYYY-MM-DD-slug [Scope]
   Trigger: "trigger condition"
   Rationale: Why this matters...
   Action: What to do when triggered
   Breadcrumbs: file1.go, file2.py

   > Incorporate into current design? [yes/no/defer]
   ```

   - **yes**: Include the seed's action and rationale as a design input for Phase 1. Mark seed as `active` in index.json.
   - **no**: Dismiss the seed (move to `.seeds/archived/`, status `dismissed`).
   - **defer**: Leave the seed dormant for future surfacing.

   If `.seeds/` does not exist or contains no dormant seeds, skip this step silently.

**Gate**: Feature state initialized. Context loaded. Seeds surfaced (if any). Check gate status before proceeding -- gates exist because downstream phases assume specific artifacts exist, so skipping them causes silent failures later.

### Phase 1: EXECUTE (Design Dialogue)

**Goal**: Collaborative exploration of the feature requirements and approach.

**Step 1: Understand Requirements**

Check gate: `python3 ~/.claude/scripts/feature-state.py gate FEATURE design.intent-discussion`

If gate mode is `human`:
- Ask clarifying questions about the feature, one at a time -- committing to an approach before understanding requirements produces designs that need rework
- Prefer multiple-choice when possible
- Establish success criteria
- Identify constraints

If gate mode is `auto`:
- Derive intent from the feature description
- Document assumptions explicitly

**Step 2: Explore Approaches**

Check gate: `python3 ~/.claude/scripts/feature-state.py gate FEATURE design.approach-selection`

Generate 2-3 approaches with trade-offs before selecting one -- a single approach provides no basis for evaluating whether it is the right one. Design only what is requested in each approach; do not add speculative requirements or future-proofing -- unasked-for complexity increases review burden, slows implementation, and often gets removed later.

```markdown
## Approach 1: [Name]
**Pros**: [advantages]
**Cons**: [disadvantages]
**Complexity**: Low/Medium/High
**Risk**: Low/Medium/High
**Domain agents needed**: [which agents from our system would implement this]
```

If gate is `human`: present approaches and ask user to select.
If gate is `auto`: select the approach that best balances simplicity and completeness.

**Step 3: Draft Design Document**

Create the design document:

```markdown
# Design: [Feature Name]

## Problem Statement
[What problem does this solve?]

## Requirements
- [ ] Requirement 1
- [ ] Requirement 2

## Selected Approach
[Which approach and why]

## Alternatives Considered
[One entry per Step 2 approach not selected, plus "do nothing" if weighed:]
- **[Name]**: Rejected because [reason] (decided by: human / auto / Jev)
- **[Name]**: Deferred because [reason] (decided by: human / auto / Jev)

## Components
[What needs to be built/modified]

## Domain Agents
[Which agents from our system will handle implementation]

## Open Questions
[Anything unresolved]

## Trade-offs Accepted
[What we're giving up and why]

## Architecture Change Handoff
[Validated source path and JSON fields, including `"origin": "architecture-deepening"`, candidate, module/caller paths, current/proposed interface, migration, and success criteria; or "none"]

## Architecture ADR
[Canonical repository-relative path and sha256 hash; filled at checkpoint]
```

**Gate**: Design document drafted. Proceed to Validate.

### Phase 2: VALIDATE

**Goal**: Verify design document is complete.

Check gate: `python3 ~/.claude/scripts/feature-state.py gate FEATURE design.design-approval`

This phase cannot complete without a design document artifact in `.feature/state/design/` -- the plan phase reads from this path, so a missing document causes the next skill to fail silently or plan against stale data.

Validation checklist:
- [ ] Problem statement is clear
- [ ] Requirements are enumerable (not vague)
- [ ] Approach is selected with rationale
- [ ] Every Step 2 approach not selected is under Alternatives Considered with a reason, so later phases and reviewers don't re-propose it
- [ ] Components are identified
- [ ] Domain agents are identified
- [ ] Open questions are listed (even if empty)
- [ ] Any Architecture Change Handoff was validated and its constraints are represented

If gate is `human`: present design to user for approval.
If gate is `auto`: verify checklist passes.

**Gate**: Design approved. Proceed to Checkpoint.

### Phase 3: CHECKPOINT

**Goal**: Save artifacts, record learnings, advance to next phase.

1. Render the approved canonical feature ADR, then validate and contain its target before the first write. `{feature-slug}` must be the safe slug created by `feature-state.py`. Pipe the content to the repository-anchored writer:

   ```bash
   python3 scripts/repository_artifact.py write \
     --repo-root . \
     --allowed-root adr \
     --path 'adr/{feature-slug}.md' <<'ADR'
   {approved ADR content}
   ADR
   ```

   The writer opens the repository and `adr/` through directory descriptors with `O_NOFOLLOW`, creates a same-directory temporary, fsyncs it, atomically replaces the target, and fsyncs the directory. A symlinked `adr/` or target blocks before any write.

2. Register the exact ADR through the canonical resolver, compute its hash, and verify that registered content before any later consumer uses it:

   ```bash
   python3 scripts/adr-query.py register --adr 'adr/{feature-slug}.md'
   python3 scripts/adr-query.py hash --adr 'adr/{feature-slug}.md'
   python3 scripts/adr-query.py validate-registration \
     --repo-root . \
     --adr 'adr/{feature-slug}.md' \
     --hash 'sha256:{digest}'
   ```

   Record the exact repository-relative ADR path and returned hash in `## Architecture ADR`. This is the only ADR the pre-IMPLEMENT consultation gate may consume. Preserve the `"origin": "architecture-deepening"` field when present so Simple architecture-origin work cannot bypass consultation.

3. Save the final design document, including the ADR path and hash:

   ```bash
   echo "DESIGN_CONTENT" | python3 ~/.claude/scripts/feature-state.py checkpoint FEATURE design
   ```

4. Advance to plan phase:
   ```bash
   python3 ~/.claude/scripts/feature-state.py advance FEATURE
   ```

5. Suggest next step:
   ```
   Design complete. Run /feature-lifecycle to continue to the plan phase.
   ```

**Gate**: Artifacts saved. Learnings recorded. Phase finished.

## Error Handling

| Error | Cause | Solution |
|-------|-------|----------|
| Feature already exists | `init` called twice | Use `status` to check, work with existing state |
| Gate returns exit 2 | Human input required | Present decision to user, wait for response |
| No design doc produced | Skipped design dialogue | Return to Phase 1, complete all steps |
| Architecture handoff validation fails | Unsafe path, incomplete design data, invalid result, or wrong successor | Stop; return the validator error to architecture-deepening |
| ADR registration validation fails | ADR path escaped `adr/`, content changed, or session registration differs | Stop; register the exact canonical feature ADR and record its fresh hash |
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