engineering-intelligence 1.0.0 → 1.2.0

package/templates/canonical/skills/requirement-scoper/SKILL.md

@@ -24,13 +24,14 @@ Act as a detailed Business Analyst and Technical Architect persona. Analyze the
 
 2. **Formulate Scoping Questions** — Identify gaps, ambiguities, and edge cases. Ask the user 3 to 5 targeted questions covering:
    - **Business Value & Scope**: What are the limits of the MVP?
+   - **Agile Story Shape**: What user role, user goal, priority, dependencies, and release expectation apply?
    - **Technical Strategy**: Which specific database, caching, or third-party integrations are expected?
    - **Edge Cases**: How should errors, rate limits, or validation failures be handled?
    - **UI/UX (if applicable)**: What configuration or user feedback is expected?
 
 3. **Iterate with User** — Wait for user responses. Adjust assumptions based on their answers.
 
-4. **Generate Final Requirement Prompt** — Once requirements are clear, output a comprehensive requirements document to `knowledge-base/19-requirements.md` and formulate the finalized prompt for the development agent.
+4. **Generate Final Requirement Prompt** — Once requirements are clear, output a comprehensive requirements document to `knowledge-base/19-requirements.md`, update Agile artifacts under `.engineering-intelligence/aidlc/agile/`, and formulate the finalized prompt for the development agent.
 
 ## Output Format
 
@@ -47,10 +48,21 @@ The final requirements document `knowledge-base/19-requirements.md` must follow
 - **System Boundaries & Dependencies**: <Files/modules affected based on graph mappings>
 - **Edge Cases & Failure Modes**: <Exactly how to handle failures, retries, limits>
 
-## 3. Iterated QA Log
+## 3. Agile Delivery Model
+- **Epic**: <epic or initiative>
+- **User Story**: As a <persona>, I want <capability>, so that <outcome>.
+- **Priority**: <P0/P1/P2 or project convention>
+- **Acceptance Criteria**:
+  - Given <context>, when <action>, then <observable result>.
+- **Definition of Ready**:
+  - <ready gate status>
+- **Definition of Done**:
+  - <done gate expectations>
+
+## 4. Iterated QA Log
 <Questions asked and answers received during scoping>
 
-## 4. Finalized Implementation Prompt
+## 5. Finalized Implementation Prompt
 Provide the exact prompt to pass to the coding agent to execute this change:
 ```text
 /engineering-intelligence <Fully detailed requirements and file scope here>
@@ -62,10 +74,12 @@ Provide the exact prompt to pass to the coding agent to execute this change:
 - **Do not modify product code** — this skill is strictly for scoping and analysis.
 - Do not make assumptions on ambiguities; always ask clarifying questions.
 - Base questions and plans on project graph mappings and existing memory files.
+- Keep Agile artifacts synchronized with the final requirement prompt.
 
 ## Quality Gates
 
 - [ ] Clear business goals and technical boundaries defined.
 - [ ] At least 3 scoping questions asked and logged.
+- [ ] User story, acceptance criteria, priority, dependencies, and Ready/Done gates are documented.
 - [ ] Finalized prompt maps exact files and modules.
 - [ ] Output does not contain any code modification.

package/templates/canonical/workflows/engineering-intelligence.md

@@ -4,18 +4,20 @@ description: Implement an engineering request with impact analysis, tests, valid
 
 # Engineering Intelligence
 
-Use the `engineering-intelligence-skill` capability for the user's accompanying request.
+Use the `engineering-intelligence-skill` capability for the user's accompanying request. For non-trivial work, use `aidlc-lifecycle-engine` inside this workflow to merge Agile delivery with AI-DLC durable state.
 
 ## Pipeline
 
 1. **Read Intelligence** — Consult `knowledge-base/`, `.engineering-intelligence/memory/`, `.engineering-intelligence/context/`, `.engineering-intelligence/graph/`
-2. **Write Impact Report** — Create `.engineering-intelligence/reports/IMP-XXX-<summary>.md` before any code edit
-3. **Implement** — Make the requested code changes following established patterns
-4. **Test** — Add/update tests proportional to risk; execute and record results
-5. **Validate** — Run available linters, type checks, and test suites
-6. **Sync Intelligence** — Incrementally update only affected knowledge, memory, context, event, graph artifacts
-7. **Record Change** — Write `.changes/CHG-XXX-<summary>.md` referencing related reports
-8. **Review Gate** — For high-risk changes, run engineering-change review before completion
+2. **Select Delivery Mode** — Choose standard Agile, adversarial, TDD, design-first, or hypothesis debugging based on risk
+3. **Write Impact Report** — Create `.engineering-intelligence/reports/IMP-XXX-<summary>.md` before any code edit
+4. **Plan Agile + AI-DLC Work** — Update backlog, acceptance criteria, Definition of Ready, `.engineering-intelligence/aidlc/execution-plan.md`, and `aidlc-state.md`
+5. **Implement** — Make the requested code changes following established patterns
+6. **Test** — Add/update tests proportional to risk; execute and record results
+7. **Validate** — Run available linters, type checks, test suites, scans, and architecture checks as environmental backpressure
+8. **Sync Intelligence** — Incrementally update only affected knowledge, memory, context, event, graph artifacts, and AI-DLC artifacts
+9. **Record Change** — Write `.changes/CHG-XXX-<summary>.md` referencing related reports
+10. **Review Gate** — For high-risk changes, run engineering-change review before completion
 
 ## Completion Report
 
@@ -25,4 +27,6 @@ Finish with:
 - Affected systems and services
 - Synchronized intelligence artifacts
 - Related reports (IMP-XXX, REV-XXX)
+- Agile artifacts updated (backlog, stories, acceptance criteria, Definition of Done)
 - Unresolved risks or follow-ups
+- AI-DLC breadcrumb (`AI-DLC: <phase> -> <stage> -> <status>`)

package/templates/canonical/workflows/initialize-engineering-intelligence.md

@@ -19,6 +19,7 @@ Analyzes this repository thoroughly without changing product code. Produces a co
 | Context | `.engineering-intelligence/context/` | 6 compact navigation maps |
 | Events | `.engineering-intelligence/events/` | 5 change-event guidance documents |
 | Graphs | `.engineering-intelligence/graph/` | 4 JSON graphs + architecture-map.md |
+| AI-DLC + Agile | `.engineering-intelligence/aidlc/` | Lifecycle state, audit, discovery placeholders, open questions, Agile backlog/sprint/DoR/DoD, cross-unit discovery log |
 | History | `.changes/CHG-000-initialization.md` | Initialization record |
 
 ## Execution Steps
@@ -29,7 +30,8 @@ Analyzes this repository thoroughly without changing product code. Produces a co
 4. **Generate Memory** — Extract durable decisions and patterns
 5. **Generate Context** — Create concise AI navigation maps
 6. **Build Graphs** — Generate evidence-backed architecture graphs
-7. **Record** — Write initialization change record
+7. **Initialize AI-DLC + Agile** — Create `aidlc-state.md`, `audit.md`, `open-questions.md`, `execution-plan.md`, Agile delivery artifacts, and `construction/cross-unit-discoveries.md`
+8. **Record** — Write initialization change record
 
 ## Important
 

package/templates/canonical/workflows/scope-requirement.md

@@ -8,17 +8,18 @@ Use the `requirement-scoper` capability to interactively scope and document a us
 
 ## Pipeline
 
-1. **Read Context** — Read `knowledge-base/`, `.engineering-intelligence/memory/`, and `.engineering-intelligence/graph/` mapping files.
-2. **Draft Questions** — Generate 3 to 5 targeted business/tech questions clarifying the requirements.
+1. **Read Context** — Read `knowledge-base/`, `.engineering-intelligence/aidlc/`, `.engineering-intelligence/memory/`, and `.engineering-intelligence/graph/` mapping files.
+2. **Draft Questions** — Generate 3 to 5 targeted business/tech questions clarifying the requirements, user story, acceptance criteria, dependencies, and Definition of Ready.
 3. **Iterate** — Prompt the user for answers in the chat pane.
-4. **Document Scoping** — Create or update `knowledge-base/19-requirements.md` with goals, logic configuration, edge cases, UI structures, and the Q&A log.
-5. **Finalize Prompt** — Output the exact `/engineering-intelligence` command required to build the feature.
+4. **Document Scoping** — Create or update `knowledge-base/19-requirements.md` and `.engineering-intelligence/aidlc/agile/` artifacts with goals, user stories, acceptance criteria, edge cases, dependencies, and the Q&A log.
+5. **Finalize Prompt** — Output the exact `/engineering-intelligence` command required to build the ready story.
 
 ## Completion Report
 
 Finish with:
 - Summary of scoped requirements
 - Location of the requirements document (`knowledge-base/19-requirements.md`)
+- Agile artifacts updated under `.engineering-intelligence/aidlc/agile/`
 - The exact implementation command prompt
 
 **Contract**: This workflow does not modify product code.