mirror of
https://github.com/azaion/ai-training.git
synced 2026-04-22 09:16:36 +00:00
Sync .cursor from suite (autodev orchestrator + monorepo skills)
This commit is contained in:
Oleksandr Bezdieniezhnykh
@@ -53,9 +53,15 @@ METRICS_DIR/
|
||||
└── ...
|
||||
```
|
||||
|
||||
## Invocation Modes
|
||||
|
||||
- **cycle-end mode** (default): invoked automatically at end of cycle by the autodev orchestrator — as greenfield Step 11 Retrospective (after Step 10 Deploy) and existing-code Step 17 Retrospective (after Step 16 Deploy). Runs Steps 1–4. Output: `retro_<YYYY-MM-DD>.md` + LESSONS.md update.
|
||||
- **incident mode**: invoked automatically after the failure retry protocol reaches `retry_count: 3` and the user has made a recovery choice. Runs Steps 1 (scoped to the failing skill's artifacts only), 2 (focused on the failure), 3 (shorter report), 4 (append 1–3 lessons in the `process` or `tooling` category). Output: `_docs/06_metrics/incident_<YYYY-MM-DD>_<skill>.md` + LESSONS.md update. Pass the invocation context with `mode: incident`, `failing_skill: <skill-name>`, and `failure_summary: <string>`.
|
||||
- **on-demand mode**: user-triggered (trigger phrases above). Runs Steps 1–4 over the entire artifact set.
|
||||
|
||||
## Progress Tracking
|
||||
|
||||
At the start of execution, create a TodoWrite with all steps (1 through 3). Update status as each step completes.
|
||||
At the start of execution, create a TodoWrite with all steps (1 through 4). Update status as each step completes.
|
||||
|
||||
## Workflow
|
||||
|
||||
@@ -74,6 +80,9 @@ At the start of execution, create a TodoWrite with all steps (1 through 3). Upda
|
||||
| Task spec files in TASKS_DIR | Complexity points per task, dependency count |
|
||||
| `implementation_report_*.md` | Total tasks, total batches, overall duration |
|
||||
| Git log (if available) | Commits per batch, files changed per batch |
|
||||
| `cumulative_review_batches_*.md` `## Baseline Delta` | Architecture findings: carried over / resolved / newly introduced counts |
|
||||
| `_docs/02_document/module-layout.md` + source import graph | Component count, cross-component edges, cycles, avg imports/module |
|
||||
| `_docs/02_document/contracts/**/*.md` | Contract count, contracts per public-API symbol |
|
||||
|
||||
#### Metrics to Compute
|
||||
|
||||
@@ -90,15 +99,35 @@ At the start of execution, create a TodoWrite with all steps (1 through 3). Upda
|
||||
- Code review findings by category: Bug, Spec-Gap, Security, Performance, Maintainability, Style, Scope
|
||||
- FAIL count (batches that required user intervention)
|
||||
|
||||
**Structural Metrics** (skip only if `module-layout.md` is absent):
|
||||
- Component count and change vs previous cycle
|
||||
- Cross-component import edges and change vs previous cycle
|
||||
- Cycles in the component import graph (should stay 0; any new cycle is a regression)
|
||||
- Average imports per module
|
||||
- New Architecture violations this cycle (from `## Baseline Delta` → Newly introduced)
|
||||
- Resolved Architecture violations this cycle (from `## Baseline Delta` → Resolved)
|
||||
- Net Architecture delta = new − resolved (negative is good)
|
||||
- Percentage of public-API symbols covered by a contract file (contract count / public-API symbol count)
|
||||
- `shared/*` entries used by ≥2 components (healthy) vs by ≤1 component (dead cross-cutting)
|
||||
|
||||
Persist the structural snapshot to `METRICS_DIR/structure_[YYYY-MM-DD].md` so future retros can compute deltas without re-deriving from source.
|
||||
|
||||
**Efficiency Metrics**:
|
||||
- Blocked task count and reasons
|
||||
- Tasks completed on first attempt vs requiring fixes
|
||||
- Batch with most findings (identify problem areas)
|
||||
|
||||
**Auto-lesson triggers** (feed Step 4 LESSONS.md generation):
|
||||
- Net Architecture delta > 0 this cycle → `architecture` lesson
|
||||
- Any structural metric regressed by >20% vs previous snapshot → `architecture` or `dependencies` lesson depending on the metric
|
||||
- Contract coverage % decreased → `architecture` lesson
|
||||
|
||||
**Self-verification**:
|
||||
- [ ] All batch reports parsed
|
||||
- [ ] All metric categories computed
|
||||
- [ ] No batch reports missed
|
||||
- [ ] Structural snapshot written (or explicitly skipped with reason "module-layout.md absent")
|
||||
- [ ] If a previous `structure_*.md` exists, deltas are computed against the most recent one
|
||||
|
||||
---
|
||||
|
||||
@@ -141,12 +170,55 @@ Write `METRICS_DIR/retro_[YYYY-MM-DD].md` using `templates/retrospective-report.
|
||||
- [ ] Top 3 improvement actions clearly stated
|
||||
- [ ] Suggested rule/skill updates are specific
|
||||
|
||||
**Save action**: Write `retro_[YYYY-MM-DD].md`
|
||||
**Save action**: Write `retro_[YYYY-MM-DD].md` (in cycle-end / on-demand mode) or `incident_[YYYY-MM-DD]_[skill].md` (in incident mode).
|
||||
|
||||
Present the report summary to the user.
|
||||
|
||||
---
|
||||
|
||||
### Step 4: Update Lessons Log
|
||||
|
||||
**Role**: Process improvement analyst
|
||||
**Goal**: Keep a short, frequently-consulted log of actionable lessons that downstream skills read before they plan or estimate.
|
||||
|
||||
1. Extract the **top 3 concrete lessons** from the current retrospective (or 1–3 lessons in incident mode, scoped to the failing skill). Each lesson must:
|
||||
- Be specific enough to change future behavior (not a platitude).
|
||||
- Be single-sentence.
|
||||
- Be tied to one of the categories: `estimation`, `architecture`, `testing`, `dependencies`, `tooling`, `process`.
|
||||
2. Append one bullet per lesson to `_docs/LESSONS.md` using this format:
|
||||
|
||||
```
|
||||
- [YYYY-MM-DD] [category] one-line lesson statement.
|
||||
Source: _docs/06_metrics/retro_YYYY-MM-DD.md
|
||||
```
|
||||
|
||||
3. After appending, trim `_docs/LESSONS.md` to keep only the last **15 entries** (ring buffer). Oldest entries drop off the top. Preserve the file's header section if present.
|
||||
4. If `_docs/LESSONS.md` does not exist, create it with this skeleton before appending:
|
||||
|
||||
```markdown
|
||||
# Lessons Log
|
||||
|
||||
A ring buffer of the last 15 actionable lessons extracted from retrospectives and incidents.
|
||||
Downstream skills consume this file:
|
||||
- `.cursor/skills/new-task/SKILL.md` (Step 2 Complexity Assessment)
|
||||
- `.cursor/skills/plan/steps/06_work-item-epics.md` (epic sizing)
|
||||
- `.cursor/skills/decompose/SKILL.md` (Step 2 task complexity)
|
||||
- `.cursor/skills/autodev/SKILL.md` (Execution Loop step 0 — surface top 3 lessons)
|
||||
|
||||
Categories: estimation · architecture · testing · dependencies · tooling · process
|
||||
```
|
||||
|
||||
**Self-verification**:
|
||||
- [ ] 1–3 lessons extracted (3 in cycle-end / on-demand mode, 1–3 in incident mode)
|
||||
- [ ] Each lesson is single-sentence, specific, and tagged with a valid category
|
||||
- [ ] Each lesson includes a Source link back to its retro or incident file
|
||||
- [ ] `_docs/LESSONS.md` trimmed to at most 15 entries
|
||||
- [ ] Skeleton header preserved if file was just created
|
||||
|
||||
**Save action**: Write (or update) `_docs/LESSONS.md`.
|
||||
|
||||
---
|
||||
|
||||
## Escalation Rules
|
||||
|
||||
| Situation | Action |
|
||||
@@ -167,6 +239,7 @@ Present the report summary to the user.
|
||||
│ 1. Collect Metrics → parse batch reports, compute metrics │
|
||||
│ 2. Analyze Trends → patterns, comparison, improvement areas │
|
||||
│ 3. Produce Report → _docs/06_metrics/retro_[date].md │
|
||||
│ 4. Update Lessons → append top-3 to _docs/LESSONS.md (≤15) │
|
||||
├────────────────────────────────────────────────────────────────┤
|
||||
│ Principles: Data-driven · Actionable · Cumulative │
|
||||
│ Non-judgmental · Save immediately │
|
||||
|
||||
Reference in New Issue
Block a user