Individual skill
ce-work
Execute a plan or concrete work prompt end-to-end. Use when implementing from a plan document, a spec path, or a clear build request; use ce-debug for open-ended bugs. Use when an outer orchestrator needs implementation and local verification only, without the shipping tail.
skills/ce-work/SKILL.md
Source commit 3449230705a508229a5a298671e9031e489f0278
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 2, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 25,969
- Repository last updated
- Nov 7, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- compound Repository topic
- engineering Repository topic
- engineering Derived category
- testing Derived category
- testing-browser Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 7,859 bytesSKILL.mdcore · 7,859 bytesreferences/agents/figma-design-sync.mddoc · 2,082 bytesreferences/agents/implementation-worker.mddoc · 3,106 bytesreferences/cross-model-execution.mddoc · 41,332 bytesreferences/execution-engines.mddoc · 6,730 bytesreferences/execution-strategy.mddoc · 16,973 bytesreferences/implementation-loop.mddoc · 17,446 bytesreferences/implementation-result-schema.jsonasset · 1,350 bytesreferences/input-triage.mddoc · 10,099 bytesreferences/multi-pr-delivery.mddoc · 6,403 bytesreferences/non-code-execution.mddoc · 2,300 bytesreferences/return-to-caller.mddoc · 4,539 bytesreferences/review-findings-followup.mddoc · 8,095 bytesreferences/shipping-workflow.mddoc · 13,870 bytesreferences/tracker-defer.mddoc · 14,487 bytesreferences/work-intake.mddoc · 9,715 bytesreferences/workspace-setup.mddoc · 4,971 bytesscripts/cross-model-work.shruns · 62,397 bytesscripts/packs-resolve.pyruns · 31,561 bytesscripts/peer-job-runner.pyruns · 109,274 bytesscripts/unit-workspace.pyruns · 8,013 bytesscripts/unit_workspace_ignored.pyruns · 3,059 bytesscripts/unit_workspace_integration.pyruns · 31,248 bytesscripts/unit_workspace_jobs.pyruns · 56,411 bytesscripts/unit_workspace_lifecycle.pyruns · 50,994 bytesscripts/unit_workspace_state.pyruns · 44,528 bytesscripts/unit_workspace_transaction.pyruns · 26,523 bytes
Read excerpt
# Work Execution Command
## Outcome
- **Result:** A fully implemented, locally verified change set from a plan, specification, or concrete work prompt.
- **Next consumer:** In standalone use, the shipping workflow takes the verified change through review and delivery. In Return-to-Caller Mode, the invoking workflow receives the structured implementation and verification result and owns its remaining gates.
- **Done:** Every in-scope task is complete, required verification evidence is recorded, relevant checks pass, and the run reaches either its owned shipping handoff (with a code-review receipt or explicit skip phrase — see Phase 3-4), a complete return result, or an explicit blocker.
- **Intent:** Finish the requested feature without renegotiating the plan or transferring canonical integration authority. Workers receive bounded units; the host orchestrator inspects actual changes and owns authoritative verification and canonical commits.
## Execution Workflow
**Bundled references must be read, never approximated.** Resolve each reference or script path named below from this skill's loaded `SKILL.md` directory, using the full skill path the harness supplied, and never glob the target repository to find a bundled file. Read each reference when you enter the phase it governs; a read made before that phase does not satisfy it, and a reference this file says to read again is read again at its step even when already in context. If the harness does not expose the skill directory, or a required file cannot be read, stop before the action it governs and report which file is missing. Do not reconstruct its rules from memory; report the missing reference instead of continuing natively.
### Phase 0: Input Triage