Sprint Contract
v1.0.0Multi-agent development workflow with Sprint Contracts and independent QA evaluation. Use when building features, fixing complex bugs, or any task that invol...
⭐ 0· 73·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description (Sprint Contract, multi-agent QA workflow) matches the SKILL.md instructions: it documents a Planner → Generator → Evaluator pattern, file-based briefs/handoffs, and evaluator rules. No unrelated resources (cloud creds, unusual binaries) are requested.
Instruction Scope
Instructions are scoped to creating/consuming BRIEF.md and HANDOFF.md, spawning builder/evaluator sub-agents, and validating explicit completion criteria. This is appropriate for a coordination workflow. Note: the skill explicitly instructs sub-agents to write files and to prefer output-first over research; if installed into an agent with filesystem or repo access, those sub-agents could modify project files — ensure you only enable it where code-writing by agents is acceptable.
Install Mechanism
No install spec or code files — instruction-only. Nothing is downloaded or written to disk by the skill itself, which minimizes supply-chain risk.
Credentials
The skill declares no required environment variables, credentials, or config paths. The runtime instructions do not request secrets or external tokens. This matches the workflow purpose.
Persistence & Privilege
always:false and default autonomous invocation are set (normal). The skill does not request permanent presence or system modifications. Note: autonomous agent invocation is allowed by default — pair this with sensible tool/FS/CI permissions when enabling the skill.
Assessment
This skill is instruction-only and coherent with its stated purpose. Before enabling it for agents that can modify repositories or files, decide whether you want automated sub-agents to create/modify code in that environment: restrict the skill to non-sensitive projects or grant it only read/write access to a sandbox. Require human gate review for high-risk or production changes, ensure BRIEF.md does not include secrets or credentials, and monitor evaluator reports for false positives/overly-strict checks. If you plan to integrate it with CI/CD or grant tool access, test it in an isolated workspace first.Like a lobster shell, security has layers — review code before you run it.
evaluationvk97ek8hwkkyt4x9t34tgmjk16583jnmblatestvk97ek8hwkkyt4x9t34tgmjk16583jnmbmulti-agentvk97ek8hwkkyt4x9t34tgmjk16583jnmbqavk97ek8hwkkyt4x9t34tgmjk16583jnmbqualityvk97ek8hwkkyt4x9t34tgmjk16583jnmbworkflowvk97ek8hwkkyt4x9t34tgmjk16583jnmb
License
MIT-0
Free to use, modify, and redistribute. No attribution required.