assess-context

User Input

$ARGUMENTS

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

Outline

IMPORTANT: Automatically generate a 'docs:' prefixed git commit message (e.g., 'docs: add codebase context assessment') and commit context-assessment.md upon completion.

1. Setup: Run {SCRIPT} from repo root and parse JSON for CONTEXT_ASSESSMENT, DOCS_DIR, REPO_ROOT, HAS_GIT.

2. Load context: Read memory/ground-rules.md (if exists), docs/architecture.md (if exists), docs/standards.md (if exists). Load CONTEXT_ASSESSMENT template (already copied). Adhere to the principles for maximizing system clarity, structural simplicity, and long-term maintainability.

3. Execute context assessment workflow: Follow the structure in CONTEXT_ASSESSMENT template to:

   • Identify technology stack and frameworks
   • Analyze project structure and organization
   • Document architectural patterns and design decisions
   • Extract coding conventions and standards
   • Map key components and their relationships
   • Identify data models and storage patterns
   • Document API contracts and integration patterns
   • Assess testing approach and coverage
   • Review build and deployment processes
   • Calculate technical health score

4. Update agent context: Run {AGENT_SCRIPT} to update agent-specific context with assessment findings.

5. Stop and report: Command ends after assessment completion. Report CONTEXT_ASSESSMENT path and technical health score.

Phases

Phase 0: Technology Stack Discovery

1. Identify core technologies:

   • Programming languages and versions (package.json, requirements.txt, pom.xml, etc.)
   • Frameworks and major libraries
   • Runtime environment (Node.js, Python, Java, .NET, etc.)
   • Database systems (PostgreSQL, MongoDB, Redis, etc.)
   • Build tools (npm, pip, Maven, Gradle, etc.)

2. Document development environment:

   • Required tools and versions
   • Environment setup requirements
   • Local development scripts
   • Configuration management approach