happycapy-ai/happycapy-skills/contract-first-agents

# === SHARED CONTRACT: [Project Name] ===
 
## 1. MODULE MANIFEST
For EVERY module/section an agent will produce:
-Exact filename
-Purpose (1 sentence)
-ALL exported names (exact spelling, exact case)
 
## 2. INTERFACE DEFINITIONS
For EVERY cross-module reference:
-Exact function/class name
-Exact parameter names and types
-Exact return type
-Source module -> consuming module(s)
 
## 3. SHARED TYPES
For EVERY data structure shared across modules:
-Exact field names and types
-Validation rules
-Serialization format
 
## 4. STYLE GUIDE
-Naming: snake_case for functions/variables, PascalCase for classes
-Indentation: [N] spaces
-Docstrings: [Google/NumPy/Sphinx] style on all public functions/classes
-Error handling: exact exception types
-Import convention: "from module import Name"
-Language-specific conventions
 
## 5. DEPENDENCY MAP
-Which modules import from which
-Execution order constraints (if any)
-Shared state / global configuration
 
## 6. SECTION BOUNDARIES
For EACH section assigned to an agent:
-What it must produce (exact deliverables)
-What it imports from other sections (exact names)
-What it exports for other sections (exact names)
-How it connects to adjacent sections (transitions, API calls, imports)

[FULL CONTRACT TEXT - every worker gets the COMPLETE contract]
 
---
 
YOUR ASSIGNMENT: [Specific section/module]
 
You are Agent [N] of [Total]. You are producing [section name].
 
CRITICAL INSTRUCTIONS:
1. Follow the contract EXACTLY. Do not deviate from specified names, types, or conventions.
2. Your section will be merged with outputs from other agents working in parallel.
3. Use ONLY the exported names specified in the contract when referencing other modules.
4. Do NOT rename, reorganize, or "improve" the interface - follow the contract.
5. Write your output to: [exact file path]

# Validation checks (in priority order):
1. Syntax validity    - Can the output be parsed? (ast.parse, eslint --no-fix, etc.)
2. Import resolution  - Do all imports match actual exports?
3. Name consistency   - Is the naming convention uniform throughout?
4. Completeness       - Are all contracted exports present?
5. Style consistency  - Indent, docstrings, error handling patterns
6. Cross-references   - Do function calls use correct signatures?

# Step 1: Create team
TeamCreate(team_name="my-project", description="Building X with contract-first protocol")
# Step 2: Team lead generates the contract
# Save contract to a shared file: ~/.claude/teams/{team-name}/contract.md
# Step 3: Spawn workers with full contract in their prompts
Task(
    name="worker-auth",
    team_name="my-project",
    subagent_type="general-purpose",
    prompt=f"""
    {FULL_CONTRACT_TEXT}
    YOUR ASSIGNMENT: auth module
    Write to: /workspace/project/auth.py
    Follow the contract exactly.
    """
)
# ... spawn all workers in parallel
# Step 4: After workers complete, validate
# Team lead reads all output files and runs validation checks
# Step 5: If issues found, spawn fixer
Task(
    name="fixer",
    team_name="my-project",
    subagent_type="general-purpose",
    prompt=f"""
    Fix these specific issues in the merged output:
    {VALIDATION_ERRORS}
    Original contract: {CONTRACT}
    Do NOT restructure. Only fix the specific issues listed.
    """
)
# Step 6: Cleanup
SendMessage(type="shutdown_request", recipient="worker-auth")
# ... shutdown all workers
TeamDelete()