lane-contract
FeaturedFile-based task contracts under .agents/runs/ with owns_paths, verification tiers L0/L1/L2, and solo merge rules. Use when user says info, справка, lane-stack:lane-contract info, or when authoring or reviewing task YAML, owns_paths, acceptance, or verification commands.
Install
Quality Score: 90/100
Skill Content
Details
- Author
- VKirill
- Repository
- VKirill/claude-lane-stack
- Created
- 2 months ago
- Last Updated
- today
- Language
- Python
- License
- MIT
Integrates with
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
execution-contract
执行契约规范 — 为长流程、多文件、Auto 或控制面任务生成/校验 ExecutionContract，约束范围、路径、产物、验证路线、偏离分级与恢复策略
loop-contract
Turns a rough multi-step need in any domain into a loop-engineered plan and then carries it out. Triages first — routes to an existing skill/plugin/agent when one fits, else designs a contract with an immutable mission, three-kind termination, an append-only ledger spine, and a hard token policy. Every job is DONE (deliverable is the change or artifact, gated by an achievement oracle written red before the work) or KNOWN (deliverable is a verdict); in both it writes the contract then executes it. Use for implementations, bug fixes, migrations, refactors, backfills, audits, PR reviews, research sweeps, non-code artifacts like plans or designs, a messy briefing, or a recurring job ("every week", "keep monitoring"). ALSO use to resume a paused job — "continue", "keep going", "what's left", "is it done yet" — it finds the spine on disk and recomputes the unfinished items. ALSO use when several agents or workers must coordinate on one job — shared conventions, item ownership, mid-run discoveries, contradicting ver
contract
Negotiate the "what done means" contract on disk before any autonomous code cycle starts. Produces contract.json with weighted criteria, user_flow (CJM-anchored), integrations (API contracts, data flow), restart threshold, and out-of-scope. Hard gate before /build-loop and /tdd. Use when starting a new feature, between /planning-with-files and the build cycle, or when user says "set up a contract", "what should done look like", "goal for this work", or invokes /contract. Triggers — contract, goal, "done means", acceptance criteria, rubric, user flow, integrations.