setup

Install groundwork git integration for this project.

The plugin root is: ${CLAUDE_PLUGIN_ROOT}

Steps:

1. Run the setup script: bash "${CLAUDE_PLUGIN_ROOT}/scripts/setup.sh" This installs git hooks and commit template deterministically.

2. Create or check WORKING_AGREEMENT.md at the project root:

   • If it doesn't exist: copy ${CLAUDE_PLUGIN_ROOT}/templates/working-agreement.md to ./WORKING_AGREEMENT.md and replace [project] in the header with the actual project name
   • If it already exists: read the template and the existing file. Check for required sections: Current Priorities, Open Friction Points, Active Commitments, Working Norms, What's Working, Last Check-in, Resolved. Report any missing sections with the template content for each. Offer to add missing sections, preserving all existing project-specific content (norms, entries, resolved items).

3. Create or update CLAUDE.md:

   • Read the groundwork template from ${CLAUDE_PLUGIN_ROOT}/templates/claude-md-groundwork.md
   • If no CLAUDE.md exists: create it with the template content
   • If CLAUDE.md exists but has no groundwork section: append the template content
   • If CLAUDE.md already has a groundwork section (detected by <!-- groundwork:start --> marker or ## Groundwork heading): replace it with the template content

   The groundwork section is owned by groundwork — replace it fully on re-run, do not merge.

4. Seed user-owned sections in CLAUDE.md (skip each if already exists):

   a. Operating Mode (skip if ## Operating Mode exists): Prepend before the groundwork section.

   ## Operating Mode
   
   Claude drives. The human's role is to support — clarifying intent, reviewing decisions,
   and providing context Claude doesn't have. Not the other way around.
   
   Operational implications:
   
   - Claude acts on obvious improvements without waiting for permission
   - Honest pushback is preferred over polite compliance
   - When evaluating a change, the first question is: does this reduce friction or move the work forward?
   

   b. Domain (skip if ## Domain exists): Add after Operating Mode, before the groundwork section.

   ## Domain
   
   <!-- Brief domain summary — what a new session needs to orient.
        For detailed domain knowledge, see docs/domain/.
        This section is user-owned — groundwork will not overwrite it.
        Update during check-in when domain understanding deepens. -->
   

5. Create docs/domain/ directory if it doesn't exist:

   mkdir -p docs/domain
   

   If the directory was just created (empty), add a README.md:

   # Domain Knowledge
   
   Detailed domain context for Claude. Files here are read by the plan skill
   before designing features — they provide the expertise a new session needs.
   
   Keep files focused: one concept per file, written for an agent that has
   never seen this domain before.
   
   Examples:
   - `game-mechanics.md` — how the core game systems work
   - `user-workflows.md` — what users actually do with this app
   - `terminology.md` — domain-specific terms and their meanings
   

6. Run validation: bash "${CLAUDE_PLUGIN_ROOT}/scripts/validate.sh" If any checks fail, fix them before reporting.

7. Report what was installed, any steps skipped, and validation results.

$ARGUMENTS