Teamwork Goal
Use when the user asks to keep going, run until it passes, fix until green, iterate until done, converge on a verifiable target, or work within an explicit budget.
Install
$ agentstack add skill-jinplu-teamwork-teamwork-goal ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-jinplu-teamwork-teamwork-goal) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Teamwork Goal
Outcome
Iterate until a verifiable target passes, the authorized budget ends, or a hard stop is reached.
Enter When
Use for explicit persistence such as “keep going,” “until green,” or a stated budget. Ordinary one-shot work stays in its narrower stage. If objective, verification, scope, Goal Invariants, or stop rules are unclear, propose them and obtain approval before creating goal state.
Do And Boundaries
Use Codex native goal state when available; otherwise keep a rolling report in docs/teamwork/reports/. Record the target, protected boundaries, Goal Invariants, verification, and the budget supplied by the user/runtime or accepted plan. Do not invent a fixed iteration budget.
Before retrying, run Replay Preflight: identify prior attempts, current evidence, do-not-repeat constraints, and the strategy delta. Route broad unknowns to research, reproducible unknown-cause failures to debug, scope decisions to plan, changes to execute, and acceptance to review. After each verify/review cycle, append the attempt result; failures and no-progress cycles also record why and what must change. Accept only when focused verification and the required review pass.
Done When
Mark complete only after the success signal passes. Otherwise return the current attempt evidence, remaining budget if defined, next strategy, or the specific stop reason.
Escalate
Stop on repeated no-progress without an evidence-backed strategy delta, destructive risk, auth/resource failure, protected-boundary conflict, or unresolved user intent. Ask before expanding authority or scope.
Conditional Protocols
Use goal-iteration.md for proposal, replay, attempt, and rolling-report formats; use each narrower stage protocol when that stage runs. Paths are under skills/using-teamwork/references/.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: JinPLu
- Source: JinPLu/Teamwork
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.