project-contract-gate

Guides a two-step interview to define product contracts before task creation.

1|Updated Jul 3, 2026
One-click install
npx skills add https://github.com/Ryokuman/new_human_ochestrator --skill project-contract-gate-ryokuman
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-contract-gate
Source: https://github.com/Ryokuman/new_human_ochestrator/tree/main/system/20-skills/project-contract-gate
Command: npx skills add https://github.com/Ryokuman/new_human_ochestrator --skill project-contract-gate-ryokuman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often jump into task creation before the product itself is clearly defined, causing tasks to substitute for missing requirements. This Skill enforces a contract gate that clarifies the product definition, MVP scope, and feature flows before any task, issue, or silo goal is written. ## Core Features & Use Cases - Two-Step Interview: First runs a natural-language product clarification, then a feature-by-feature clarification where the agent proposes inferences and the user confirms with numbered answers. - Gate Reporting: Reports the current hypothesis, current gate, next gate, and rationale before asking questions, and blocks task creation until pass criteria are met. - SSoT Output: Writes confirmed requirements as per-feature documents into the tier-1 Project SSoT (e.g., entry-login, goal, dashboard-calendar, sync-storage) on the correct project branch. - Use Case: A user says they want to build a habit-tracking app but has no written requirements. The Skill interviews them on login, goal lifecycle, dashboard, storage/sync, and design sources, then produces requirement documents and identifies the first task slice. ## Quick Start Ask the agent to run the project contract gate to clarify the product definition and MVP scope before creating any tasks.

Frequently Asked Questions about project-contract-gate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I define product requirements before creating tasks?

Run a contract gate interview that first captures the product in natural language, then confirms each feature through agent-proposed inferences with numbered answers. Only after the gate passes should tasks, issues, or silo goals be created.

What is a project contract gate in product planning?

A project contract gate is a checkpoint that ensures the product definition, MVP scope, feature flows, and data boundaries are explicit before implementation work begins. It prevents tasks from substituting for missing product requirements.

Can I use this gate when requirements already exist?

Yes. The Skill first locates existing requirement, design, DB, API, and runtime documents in the project SSoT, then layers additional questions on top to close gaps or resolve contradictions rather than restarting the interview.

What happens if the contract gate does not pass?

No task is created and the status is reported as Project Contract reinforcement needed. Pass criteria include a one-sentence product definition, separated MVP and follow-up scope, feature user flows, and declared storage and design source-of-truth locations.

Where are the confirmed requirements stored?

Confirmed requirements are written as per-feature or per-flow documents in the tier-1 Project SSoT requirements directory on the project branch. Implementation issues, tasks, QA, and runbooks belong separately in the tier-2 Project Work SSoT.