the-sit-down

Draft binding Contracts with versioned frontmatter and traceability to work packages.

71|9|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/kucherenko/gangsta --skill the-sit-down
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: the-sit-down
Source: https://github.com/kucherenko/gangsta/tree/main/skills/the-sit-down
Command: npx skills add https://github.com/kucherenko/gangsta --skill the-sit-down

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Drafting formal contracts during the Sit-Down when code generation is strictly prohibited, ensuring a binding specification governs all subsequent phases.

Core Features & Use Cases

  • Produces the binding Contract document that defines objectives, requirements, decisions, and risks.
  • Enforces a no-code policy for the Sit-Down and ties to later Resource Development and approvals.
  • Supports Consigliere reviews and Don signing workflow for end-to-end governance.

Quick Start

To begin, initiate the Sit-Down Contract drafting after Grilling consensus is approved, and request the binding Contract draft.

Frequently Asked Questions about the-sit-down

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

FAQPage Schema
How do I draft a binding contract for project governance without writing code?

To draft a binding contract without code, you initiate the Sit-Down phase after Grilling consensus is approved. This produces a formal specification document that enforces a no-code policy and governs all subsequent project execution.

What is a no-code compliance contract and when do I need one?

A no-code compliance contract is a formal specification document that defines project objectives, decisions, and risks while strictly prohibiting code generation. You need one during the Sit-Down phase when a binding agreement is required for execution planning.

Can I use the Sit-Down specification to enforce traceability for work packages?

Yes, the Sit-Down specification enforces traceability by applying versioned frontmatter to the binding contract. This ensures all subsequent work packages are formally tracked and governed throughout the execution planning phases.

How do I start the contract drafting process after Grilling consensus is approved?

You start contract drafting by requesting the binding Contract draft immediately after Grilling consensus is approved. The system then generates the formal document with versioned frontmatter, ready for Consigliere reviews and Don signing.

Does the Consigliere review workflow support formal specification governance?

Yes, the Consigliere review workflow supports specification governance by validating the binding Contract before the Don signing phase. This ensures the no-code specification meets all formal requirements for downstream execution planning.

Why does the Sit-Down phase strictly prohibit code generation?

The Sit-Down phase prohibits code generation to ensure a binding specification governs all subsequent phases. This no-code policy prevents premature implementation and guarantees formal specification drafting precedes any execution planning.