engineering-intelligence 0.2.0 → 0.3.0

package/templates/canonical/skills/engineering-intelligence/SKILL.md

@@ -1,21 +0,0 @@
----
-name: engineering-intelligence
-description: Executes engineering changes with impact analysis, implementation, tests, validation, and incremental synchronization of project intelligence. Use for feature, bugfix, update, refactor, architecture, infrastructure, or security requests.
----
-
-# Engineering Intelligence Workflow
-
-Use this workflow for implementation requests after project intelligence has been initialized.
-
-## Procedure
-
-1. Read relevant files from `knowledge-base/`, `.engineering-intelligence/memory/`, `.engineering-intelligence/context/`, and `.engineering-intelligence/graph/`. If missing, run the initialization capability first.
-2. Classify the request and write a pre-change `.engineering-intelligence/reports/IMP-XXX-<summary>.md` impact report before editing.
-3. Implement the requested change in the project code.
-4. Add or update relevant tests and execute the appropriate validation available in the project.
-5. Use incremental synchronization to update only affected knowledge-base, memory, context, event, graph, and report artifacts.
-6. Create the next `.changes/CHG-XXX-<summary>.md` record referencing related impact and any review reports.
-7. For high-risk changes, run engineering-change review before final reporting.
-8. Report code changes, tests run, affected systems, synchronized documentation/graph artifacts, and unresolved risks.
-
-Do not claim validation succeeded unless it ran successfully. Do not update unrelated documents merely to regenerate them.

package/templates/canonical/skills/initialize-engineering-intelligence/SKILL.md

@@ -1,32 +0,0 @@
----
-name: initialize-engineering-intelligence
-description: Initializes project engineering intelligence by analyzing repository evidence and generating knowledge, context, memory, event guidance, architecture graphs, and an initialization change record. Use when onboarding a repository or when asked to initialize engineering intelligence.
----
-
-# Initialize Engineering Intelligence
-
-Create a trustworthy project intelligence baseline. Analyze only evidence present in source code, configuration, tests, infrastructure, and existing documentation. Mark unknowns and uncertainties explicitly; never invent architecture, APIs, schemas, or business rules.
-
-## Outputs
-
-Generate:
-
-- `knowledge-base/00-project-overview.md` through `knowledge-base/15-validation-report.md`
-- `.engineering-intelligence/memory/` for durable decisions, rules, patterns, constraints, and technology decisions
-- `.engineering-intelligence/context/` for module, service, runtime, dependency, critical-path, and dangerous-area maps
-- `.engineering-intelligence/events/` for API, schema, auth, feature, and infrastructure change guidance
-- `.engineering-intelligence/graph/` for JSON dependency, service, runtime, and business-flow graphs plus a Mermaid architecture map
-- `.changes/CHG-000-initialization.md`
-
-## Procedure
-
-1. Discover repositories, packages, runtimes, build systems, entrypoints, CI, deployment, environment examples, databases, APIs, auth, and tests.
-2. Trace architecture and critical runtime flows from code evidence.
-3. Write the knowledge base with file-backed evidence and clearly labeled unknowns.
-4. Validate major documentation claims against the project and write `15-validation-report.md`.
-5. Generate compact durable memory and navigation context from validated findings.
-6. Use `graph-engine` to generate a full evidence-backed graph baseline and `architecture-map.md`.
-7. Generate change-event guidance and initialization history.
-8. Report generated artifacts, confidence limits, and areas requiring human confirmation.
-
-This initialization workflow documents and validates the project. It does not implement product changes.