sso-mcp-server: Agent for Claude Code

User Input

$ARGUMENTS

You MUST consider the user input before proceeding (if not empty).

Outline

You are creating or updating the project ground rules at memory/ground-rules.md based on the template at .rainbow.rainbow/templates/templates-for-commands/ground-rules-template.md. The template contains placeholder tokens in square brackets (e.g. [PROJECT_NAME], [PRINCIPLE_1_NAME]). Your job is to (a) copy the template, (b) collect/derive concrete values, (c) fill the template precisely, and (d) propagate any amendments across dependent artifacts.

Follow this execution flow:

IMPORTANT: Automatically generate a 'docs:' prefixed git commit message (e.g., 'docs: establish project ground rules v1.0.0' or 'docs: update ground rules to v1.1.0') and commit memory/ground-rules.md and any updated template files upon completion.

1. Load the ground rules template from .rainbow.rainbow/templates/templates-for-commands/ground-rules-template.md.

   • If memory/ground-rules.md already exists, read it to extract current values and version information.
   • Identify every placeholder token of the form [ALL_CAPS_IDENTIFIER] from the template. IMPORTANT: The user might require less or more principles than the ones used in the template. If a number is specified, respect that - follow the general template structure. You will update the doc accordingly.

2. Collect/derive values for placeholders:

   • If user input (conversation) supplies a value, use it.
   • If memory/ground-rules.md exists, extract current values from it (preserve existing principles unless user requests changes).
   • Otherwise infer from existing repo context (README, docs, project structure).
   • For governance dates:
     • RATIFICATION_DATE is the original adoption date (if unknown and this is first creation, use today; if updating existing ground-rules, preserve original date).
     • LAST_AMENDED_DATE is today if changes are made, otherwise keep previous date.
   • CONSTITUTION_VERSION must increment according to semantic versioning rules:
     • MAJOR: Backward incompatible governance/principle removals or redefinitions.
     • MINOR: New principle/section added or materially expanded guidance.
     • PATCH: Clarifications, wording, typo fixes, non-semantic refinements.
   • If this is the first ground rules document (no existing memory/ground-rules.md), start with version 1.0.0.
   • If version bump type ambiguous, propose reasoning before finalizing.