Skip to main content
Exécutez n'importe quel Skill dans Manus
en un clic
Dépôt GitHub

autoworker

autoworker contient 11 skills collectées depuis phj128, avec une couverture métier par dépôt et des pages de détail sur le site.

skills collectés
11
Stars
16
mis à jour
2026-03-28
Forks
3
Couverture métier
3 catégories métier · 100% classifié
explorateur de dépôts

Skills dans ce dépôt

autoworker
Développeurs de logiciels

Auto-loop execution workflow with quality gates. Use when starting any non-trivial implementation task. Provides automatic task decomposition, code implementation, testing (L1-L4), and iterative quality gates until completion. Invoke with /autoworker.

2026-03-28
checkpoint
Développeurs de logiciels

Record progress to subtask: Phase completion (from autoworker:code) or test results (from autoworker:test). Auto-detects upstream type from conversation context. Ends by calling autoworker:dispatch.

2026-03-24
code
Développeurs de logiciels

Implement ONE pending Phase from subtask plan. Only write code, do not mark checkboxes or run tests. Called by autoworker:dispatch. Ends by calling autoworker:checkpoint.

2026-03-24
deep-plan
Spécialistes en gestion de projets

Structured deep discussion for Plan Mode. Runs inside EnterPlanMode to ensure thorough questioning before writing a plan. Covers motivation, assumptions, design, acceptance criteria. Call this immediately after entering Plan Mode for any non-trivial task.

2026-03-24
dispatch
Développeurs de logiciels

Read subtask.md checkbox state and route to next skill. The ONLY routing point in the execution loop. Called after autoworker:checkpoint, autoworker:gate-check, autoworker:subtask-update, autoworker:subtask-plan, or when resuming after context loss. When lost, call autoworker:dispatch.

2026-03-24
gate-check
Analystes en assurance qualité des logiciels et testeurs

Final quality gate before reporting task completion (Gate 3). Fills confidence assessment, runs supplementary verification for <95% items, completes self-check checklist. Writes PASS/FAIL result to subtask.md, then calls autoworker:dispatch for routing.

2026-03-24
subtask-init
Développeurs de logiciels

Create subtask document (first half): user confirmation, goals, assumptions. Auto-runs assumption verification experiments and fills in results. Call after Gate 1.1 (user confirmation) is done, before writing any code.

2026-03-24
subtask-plan
Spécialistes en gestion de projets

Complete subtask verification plan: upstream traceability table + L1-L4 test plan + self-check. Call after autoworker:subtask-init. Makes subtask ready for code implementation.

2026-03-24
subtask-update
Développeurs de logiciels

Update subtask with fixes or new steps. Two trigger modes: (A) Auto-called by autoworker:gate-check on FAIL — reads FAIL info, adds supplementary steps. (B) User calls with a finding/bug during testing — diagnoses, fixes, updates subtask. Both modes end by invoking autoworker:dispatch to re-enter the loop.

2026-03-24
sync-docs
Spécialistes en gestion de projets

Sync tracking documents based on current conversation results. Updates subtask, progress, findings, task_plan, project CLAUDE.md. Use when finishing a task or reaching a milestone.

2026-03-24
test
Analystes en assurance qualité des logiciels et testeurs

Execute ONE test level (L1/L2/L3/L4) from subtask verification plan. Only run tests, do not record results. Called by autoworker:dispatch with level argument. Ends by calling autoworker:checkpoint.

2026-03-24