notque/vexjoy-agent / skills/meta/do
do
VerifiedClassify user requests and route to the correct skill, pipeline, and stack. Primary entry point for all delegated work.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 31.2 KB |
| references/antigravity-execution.md | markdown | 21.2 KB |
| references/error-handling.md | markdown | 478 B |
| references/execution-architecture.md | markdown | 1.2 KB |
| references/hooks-guide.md | markdown | 2.7 KB |
| references/lazy-completion-detector.md | markdown | 2.2 KB |
| references/model-selection.md | markdown | 8.4 KB |
| references/parallel-analysis.md | markdown | 13.4 KB |
| references/perspective-prompts.md | markdown | 5.8 KB |
| references/pipeline-guide.md | markdown | 1.6 KB |
| references/planning-guide.md | markdown | 1.2 KB |
| references/progressive-depth.md | markdown | 5.4 KB |
| references/quality-gates.md | markdown | 536 B |
| references/quality-loop.md | markdown | 6.8 KB |
| references/repo-architecture.md | markdown | 4.9 KB |
| references/routing-telemetry.md | markdown | 4.6 KB |
| references/semantic-first-ab-results.md | markdown | 1.6 KB |
| references/workflow-dispatch.md | markdown | 9.5 KB |
| references/worktree-rules.md | markdown | 5.0 KB |
references/planning-guide.md
View on GitHub# Manus-Style Planning
The `pretool-plan-gate` hook (PreToolUse) blocks Write/Edit to `agents/` and `skills/` when `task_plan.md` is missing, enforcing plan-first development.
## When Plans Are Required
| Complexity | Indicators | Action |
|------------|------------|--------|
| Trivial | Pure lookup, single read | No plan needed |
| Simple+ | Routes to a skill, code change | **Create task_plan.md** |
## Plan File Template
```markdown
# Task Plan: [Brief Description]
## Goal
[One sentence describing the end state]
## Phases
- [ ] Phase 1: Understand/research
- [ ] Phase 2: Plan approach
- [ ] Phase 3: Implement
- [ ] Phase 4: Verify and deliver
## Key Questions
1. [Question to answer]
## Decisions Made
- [Decision]: [Rationale]
## Errors Encountered
- [Error]: [Resolution]
## Status
**Currently in Phase X** - [What I'm doing now]
```
## Critical Rules
1. **ALWAYS create plan first** - Never start complex work without `task_plan.md`
2. **Read before decide** - Re-read plan before major decisions (combats context drift)
3. **Update after act** - Mark [x] and update status after each phase
4. **Store, don't stuff** - Large outputs go to files, not context
5. **Log all errors** - Every error goes in "Errors Encountered" section
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |