engineering-intelligence 0.8.1 → 1.0.0

package/templates/canonical/workflows/create-project.md

@@ -0,0 +1,63 @@
+---
+description: Create a new project from scratch with full AIDLC — from architectural interview through scaffolding, intelligence initialization, and convention detection.
+---
+
+# Create Project
+
+Chain `greenfield-architect` → scaffold → `initialize-intelligence-skill` → `convention-detector` to produce a fully instrumented project with engineering intelligence from day one.
+
+## Input
+
+A description of the project to create: purpose, domain, technology preferences, and constraints. If insufficient context is provided, the architectural interview in step 1 will gather it.
+
+## Output
+
+A complete, scaffolded project with:
+
+| Category | Content |
+|---|---|
+| Project scaffold | Directory structure, configuration, dependencies, build system |
+| Knowledge Base | `knowledge-base/` — initialized project intelligence |
+| Memory | `.engineering-intelligence/memory/` — initial decisions and patterns |
+| Context | `.engineering-intelligence/context/` — AI navigation maps |
+| Graphs | `.engineering-intelligence/graph/` — initial architecture graphs |
+| Conventions | `knowledge-base/06-conventions-and-standards.md` — detected and configured conventions |
+| Change Record | `.changes/CHG-000-initialization.md` — project creation record |
+
+## Execution Steps
+
+1. **Architectural Interview** — Invoke `greenfield-architect` to conduct a structured interview:
+   - Gather requirements: domain, scale, team size, deployment targets
+   - Explore technology choices: language, framework, database, infrastructure
+   - Define architecture: monolith vs microservices, API style, data patterns
+   - Record decisions as ADRs in `knowledge-base/05-architecture-decisions.md`
+   - Produce a project blueprint before proceeding
+
+2. **Scaffold Project** — Based on the architectural blueprint:
+   - Create directory structure following chosen conventions
+   - Initialize package manifests and dependency management
+   - Configure build system, linting, and formatting
+   - Set up test infrastructure
+   - Create initial CI/CD pipeline configuration
+   - Add README, LICENSE, and contributing guidelines
+   - Initialize git repository with initial commit
+
+3. **Initialize Intelligence** — Invoke `initialize-intelligence-skill`:
+   - Generate knowledge-base documents from the scaffolded project
+   - Build initial architecture graphs
+   - Create AI context and navigation maps
+   - Write initialization change record (CHG-000)
+
+4. **Detect Conventions** — Invoke `convention-detector`:
+   - Codify the conventions established during scaffolding
+   - Document naming patterns, file organization, and code style
+   - Record testing conventions and patterns
+   - Update `knowledge-base/06-conventions-and-standards.md`
+
+## Rules
+
+- Complete the architectural interview before scaffolding — do not assume technology choices
+- Every architectural decision must be recorded as an ADR
+- The scaffold must be functional — buildable and testable from the start
+- Intelligence initialization must produce evidence-backed artifacts, not templates
+- This workflow creates a new project and modifies the scaffolded project code

package/templates/canonical/workflows/discover-codebase.md

@@ -0,0 +1,60 @@
+---
+description: Autonomously discover and understand an existing codebase through systematic analysis, interactive clarification, and finalized intelligence artifacts — without modifying product code.
+---
+
+# Discover Codebase
+
+Use `codebase-discovery-engine` to build a complete understanding of an existing project, then present findings, resolve ambiguities through clarification, and finalize the intelligence baseline.
+
+## Input
+
+An existing repository to analyze. If the repository path is ambiguous, ask for clarification.
+
+## Output
+
+Finalized codebase understanding captured in intelligence artifacts:
+
+| Category | Path | Content |
+|---|---|---|
+| Knowledge Base | `knowledge-base/` | Evidence-backed project documentation |
+| Graphs | `.engineering-intelligence/graph/` | Architecture graphs and maps |
+| Context | `.engineering-intelligence/context/` | AI navigation maps |
+| Discovery Report | `.engineering-intelligence/reports/DISCOVERY-*.md` | Findings summary with confidence levels |
+
+## Execution Steps
+
+1. **Discover** — Invoke `codebase-discovery-engine` to scan the repository:
+   - Technology stack, frameworks, and runtimes
+   - Project structure and module organization
+   - API surfaces, database schemas, and integrations
+   - Build systems, CI/CD pipelines, and deployment targets
+   - Test infrastructure and coverage
+   - Authentication and authorization patterns
+
+2. **Present Findings** — Surface the discovery results to the user:
+   - Summarize what was found with confidence levels
+   - Highlight areas of uncertainty or ambiguity
+   - Call out architectural patterns and notable design decisions
+   - Identify gaps where information could not be determined from code alone
+
+3. **Ask Clarifications** — For areas with low confidence or ambiguity:
+   - Ask targeted questions about unclear architectural decisions
+   - Confirm assumptions about deployment topology
+   - Verify business domain understanding
+   - Clarify team conventions not evident from code
+
+4. **Finalize Understanding** — Incorporate clarifications and produce final artifacts:
+   - Update knowledge-base documents with confirmed information
+   - Mark remaining unknowns explicitly
+   - Generate architecture graphs via `graph-engine`
+   - Write discovery report with confidence assessment
+
+## Rules
+
+- Begin with automated analysis — ask questions only for genuine ambiguity
+- Every claim must cite evidence from the repository
+- Do not fabricate details — mark uncertainty clearly
+- Present findings before asking clarifications (show work first)
+- This workflow does not modify product code
+
+This workflow does not modify product code. It writes only intelligence artifacts.