Skip to content

Commit c1352fa

Browse files
authored
Merge pull request #106 from cyberfabric/feature/plans
feat(plans): execution plans workflow, plan escalation gate, routing fix
2 parents 1c9b040 + 870b8ef commit c1352fa

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

59 files changed

+8030
-44
lines changed

.agents/skills/cypilot/SKILL.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
name: cypilot
3-
description: "Invoke when user asks to do something with Cypilot, or wants to analyze/validate artifacts, or create/generate/implement anything using Cypilot workflows. Core capabilities: workflow routing (analyze/generate/auto-config); deterministic validation (structure, cross-refs, traceability, TOC); code↔artifact traceability with @cpt-* markers; spec coverage measurement; ID search/navigation; init/bootstrap; adapter + registry discovery; auto-configuration of brownfield projects (scan conventions, generate rules); kit management (install/update with file-level diff); TOC generation; agent integrations (Windsurf, Cursor, Claude, Copilot, OpenAI). Kit sdlc: Artifacts: ADR, CODEBASE, DECOMPOSITION, DESIGN, FEATURE, PR-CODE-REVIEW-TEMPLATE, PR-REVIEW, PR-STATUS-REPORT-TEMPLATE, PRD; Workflows: pr-review, pr-status."
3+
description: "Invoke when user asks to do something with Cypilot, or wants to analyze/validate artifacts, or create/generate/implement anything using Cypilot workflows, or plan phased execution. Core capabilities: workflow routing (plan/analyze/generate/auto-config); deterministic validation (structure, cross-refs, traceability, TOC); code↔artifact traceability with @cpt-* markers; spec coverage measurement; ID search/navigation; init/bootstrap; adapter + registry discovery; auto-configuration of brownfield projects (scan conventions, generate rules); kit management (install/update with file-level diff); TOC generation; agent integrations (Windsurf, Cursor, Claude, Copilot, OpenAI). Kit sdlc: Artifacts: ADR, CODEBASE, DECOMPOSITION, DESIGN, FEATURE, PR-CODE-REVIEW-TEMPLATE, PR-REVIEW, PR-STATUS-REPORT-TEMPLATE, PRD; Workflows: pr-review, pr-status."
44
---
55

66

Lines changed: 203 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,203 @@
1+
# Cypilot Cross-Validation Audit Report
2+
3+
**Date**: 2026-03-12
4+
**Scope**: Full codebase + specifications audit
5+
**Phases completed**: 11/11
6+
7+
## Executive Summary
8+
9+
The Cypilot project is in **good health** with strong architectural foundations. All 14 p1 functional requirements have code implementations, all 14 ADRs are reflected in the DESIGN, and both codebases (proxy and skill engine) comply with architectural constraints (stdlib-only, stateless proxy, no SDLC code in core). The primary systemic issue is **incomplete ADR-0001 propagation**: the blueprint system was correctly removed from code, but spec artifacts (CLISPEC, DECOMPOSITION, 3 FEATURE specs) still reference the removed system. This single root cause accounts for roughly one-third of all HIGH-severity findings across phases. Secondary concerns are PRD quality issues (implementation details embedded in requirements) and documentation gaps (CLISPEC not reflecting actual CLI surface). No blocking defects were found.
10+
11+
### Issue Summary
12+
13+
| Severity | Raw Count | After Dedup (est.) |
14+
|----------|-----------|-------------------|
15+
| CRITICAL | 6 | 6 |
16+
| HIGH | 29 | ~15 |
17+
| MEDIUM | 29 | ~20 |
18+
| LOW | 30 | ~20 |
19+
| **Total** | **94** | **~61** |
20+
21+
Major deduplication: the stale `blueprint-system` ID and ADR-0001 propagation failure account for ~15 raw findings across phases 2, 6, 8, 9, and 10.
22+
23+
### Top Findings
24+
25+
1. **ADR-0001 propagation failure** — Blueprint system removed from code but not from CLISPEC, DECOMPOSITION, or 3 FEATURE specs — Phases 2, 6, 8, 9, 10
26+
2. **Implementation details in PRD** — TOML format, directory paths, VS Code UI specs embedded in requirements instead of deferred to DESIGN — Phase 4
27+
3. **ADR-0013 filename/ID slug mismatch** — File says `extract-sdlc-kit-to-github`, ID says `extract-sdlc-kit`, breaking automated resolution — Phase 7
28+
29+
## Metrics Dashboard
30+
31+
| Metric | Value | Assessment |
32+
|--------|-------|-----------|
33+
| PRD → Code traceability | 15/21 FRs full chain (71%) | needs-work — 4 expected p2/p3 backlog, 1 partial, 1 broken DECOMP link |
34+
| PRD → DESIGN coverage | 21/21 FRs (100%) | good |
35+
| DESIGN → DECOMP coverage | 7/7 components (100%) | good |
36+
| Spec quality (PRD) | 9 issues (3C, 3H, 3M) | needs-work — implementation details in requirements |
37+
| Spec quality (DESIGN) | 7 issues (0C, 0H, 2M, 5L) | good |
38+
| Spec quality (DECOMP+FEATURE) | 20 issues (2C, 8H, 7M, 3L) | needs-work — stale IDs, missing checkboxes |
39+
| Spec quality (ADRs) | 13 issues (1C, 4H, 5M, 3L) | needs-work — status staleness, informal refs |
40+
| ADR → DESIGN compliance | 12/14 fully reflected (86%) | good — 2 partial (ADR-0004 dual-mode, ADR-0012 marker format) |
41+
| Code → Spec coverage (proxy) | 22/25 symbols traced (88%) | good |
42+
| Code → Spec coverage (skill) | 22/22 commands traced (100%) | good |
43+
| SDLC boundary compliance | 0 violations | good |
44+
| Priority inversions | 0 | good |
45+
46+
## Findings by Category
47+
48+
### 1. Traceability Gaps
49+
50+
**Sources**: Phases 1, 2, 10
51+
52+
**Pattern**: The PRD→DESIGN link is solid (100% FR coverage). The DESIGN→DECOMPOSITION link is solid (100% component coverage). Gaps emerge at the DECOMPOSITION→Code level for p2/p3 items and in NFR allocation.
53+
54+
| ID | Finding | Severity | Phases |
55+
|----|---------|----------|--------|
56+
| T-01 | `fr-core-toc` unallocated in DECOMPOSITION despite being fully implemented | MEDIUM | 2, 10 |
57+
| T-02 | 5 NFRs unallocated by NFR ID in DECOMPOSITION (addressed via Design Principle refs instead) | HIGH | 2 |
58+
| T-03 | Interface ID divergence between PRD and DESIGN for CLI and GitHub interfaces | HIGH | 1 |
59+
| T-04 | 2 FEATURE specs have weak backlinks (generic refs, not specific FR/component IDs) | MEDIUM | 2 |
60+
| T-05 | Resource Diff Engine lacks formal component ID in DESIGN | LOW | 2 |
61+
| T-06 | DESIGN Section 5 omits ADRs 0013 and 0014 from traceability list (listed in §1.2) | HIGH | 3 |
62+
| T-07 | PRD acceptance criteria cover only 6/21 FRs | HIGH | 4 |
63+
| T-08 | Missing use cases for 3 p2 FRs (`doctor`, `template-qa`, `vscode-plugin`) | HIGH | 4 |
64+
65+
### 2. Specification Quality Issues
66+
67+
**Sources**: Phases 4, 5, 6, 7
68+
69+
**Pattern**: The DESIGN document is the highest-quality spec (0 CRITICAL issues). The PRD has the most structural problems (implementation details leaking into requirements). FEATURE specs suffer from stale IDs and inconsistent implementation tracking.
70+
71+
| ID | Finding | Severity | Phase |
72+
|----|---------|----------|-------|
73+
| Q-01 | Implementation decisions embedded in PRD FRs (TOML format, directory paths, line budgets) | CRITICAL | 4 |
74+
| Q-02 | Technical implementation details in PRD (filenames, VS Code UI specs) | CRITICAL | 4 |
75+
| Q-03 | Architectural decision stated in PRD ("single-layer generic engine") | CRITICAL | 4 |
76+
| Q-04 | `fr-core-kits` is monolithic — 9 sub-requirements spanning 4+ concerns | MEDIUM | 4 |
77+
| Q-05 | Vague term "intuitive" in `nfr-simplicity` (untestable) | MEDIUM | 4 |
78+
| Q-06 | VS Code Plugin FR contains spec-level design (10 UI behaviors) | HIGH | 4 |
79+
| Q-07 | Acronyms (PRD, SDLC, CI/CD, etc.) not expanded on first use | MEDIUM | 4 |
80+
| Q-08 | No system context diagram in DESIGN | MEDIUM | 5 |
81+
| Q-09 | Module/package structure not documented in DESIGN | MEDIUM | 5 |
82+
| Q-10 | v2-v3-migration.md missing standard "Implementation Modules" section | CRITICAL | 6 |
83+
| Q-11 | Kit Management flow/algo checkbox inconsistency (flow unchecked, algo checked) | CRITICAL | 6 |
84+
| Q-12 | 3 DECOMPOSITION features show ⏳ but have checked `[x]` feature checkboxes | MEDIUM | 6 |
85+
| Q-13 | ~20 CDSL steps in `agent-integration.md` and `developer-experience.md` lack checkboxes | HIGH | 6 |
86+
| Q-14 | ADR-0013 filename slug (`extract-sdlc-kit-to-github`) ≠ ID slug (`extract-sdlc-kit`) | CRITICAL | 7 |
87+
| Q-15 | ADR-0001 and ADR-0009 lack explicit risk documentation in consequences | HIGH | 7 |
88+
| Q-16 | 3 ADRs use informal traceability references instead of canonical `cpt-*` IDs | MEDIUM | 7 |
89+
| Q-17 | ADR-0013 and ADR-0014 ID placement before TOC (inconsistent with ADRs 0001–0012) | MEDIUM | 7 |
90+
91+
### 3. Code-Specification Drift
92+
93+
**Sources**: Phases 8, 9, 10
94+
95+
**Pattern**: A single root cause — **ADR-0001 not propagated to spec artifacts** — produces most drift. Code was correctly updated when the blueprint system was removed, but CLISPEC, DECOMPOSITION, and FEATURE specs were not. Secondary drift: undocumented commands and flags in the actual CLI.
96+
97+
| ID | Finding | Severity | Phases |
98+
|----|---------|----------|--------|
99+
| D-01 | CLISPEC `update` description references removed blueprint system | HIGH | 8, 10 |
100+
| D-02 | CLISPEC defines removed commands (`kit migrate`, `generate-resources`) | HIGH | 8, 10 |
101+
| D-03 | DECOMPOSITION Feature 2.2 uses stale ID `cpt-cypilot-feature-blueprint-system` | HIGH | 2, 6, 10 |
102+
| D-04 | 3 FEATURE specs declare stale `blueprint-system` dependency (F5, F7, F10) | HIGH | 2, 6, 10 |
103+
| D-05 | `agents` command implemented but not in CLISPEC | MEDIUM | 9, 10 |
104+
| D-06 | Proxy flags (`--source`, `--url`, `--no-cache`, `--version`) not in CLISPEC | MEDIUM | 8, 10 |
105+
| D-07 | `self-check` routed as alias to `validate-kits` (CLISPEC implies standalone) | MEDIUM | 9, 10 |
106+
| D-08 | "Background" version check is synchronous post-execution (wording drift) | LOW | 8 |
107+
| D-09 | Stale blueprint references in `toc.py` docstrings | LOW | 9, 10 |
108+
| D-10 | DECOMPOSITION F12 references non-existent `workflow-engine` component | MEDIUM | 2, 6 |
109+
| D-11 | Fork URL support and local copy capability undocumented in specs | LOW | 8, 10 |
110+
| D-12 | ADR-0013 status `proposed` but decision fully acted upon (SDLC kit extracted) | HIGH | 3, 7 |
111+
| D-13 | ADR-0014 status `proposed` but DESIGN treats as accepted | HIGH | 3, 7 |
112+
| D-14 | PRD checkboxes `[ ]` for 4 FRs that are fully implemented | LOW | 10 |
113+
114+
### 4. Architecture Compliance
115+
116+
**Sources**: Phases 3, 8, 9
117+
118+
**Pattern**: Architecture compliance is strong. All ADRs are reflected in DESIGN, code follows the stateless proxy pattern, stdlib-only constraint is met, and SDLC kit extraction is clean.
119+
120+
| ID | Finding | Severity | Phases |
121+
|----|---------|----------|--------|
122+
| A-01 | ADR-0004 dual-mode CLI output not fully captured in DESIGN | MEDIUM | 3 |
123+
| A-02 | ADR-0012 git-style conflict marker format not specified in DESIGN | MEDIUM | 3 |
124+
| A-03 | Missing `cypilot` console entry point (only `cpt` registered) | HIGH | 8, 10 |
125+
| A-04 | `kit move-config` specified in DESIGN §3.3 + DECOMPOSITION but not implemented (p1 scope) | HIGH | 9, 10 |
126+
| A-05 | 5 DESIGN §3.3 commands unimplemented: `doctor`, `config show`, `config system add/remove`, `hook install/uninstall` | MEDIUM | 9 |
127+
128+
### 5. Dead Code & Cleanup
129+
130+
**Sources**: Phases 8, 9
131+
132+
**Pattern**: Very little dead code. The codebase is clean. Remaining items are intentional deprecated stubs and minor documentation debt.
133+
134+
| ID | Finding | Severity | Phase |
135+
|----|---------|----------|-------|
136+
| C-01 | Legacy fallback scan in `find_install_dir` — searches for old directory names | LOW | 8 |
137+
| C-02 | 2 intentional deprecated command stubs (`validate-code`, `validate-rules`) | LOW | 9 |
138+
| C-03 | Init/Update special routing not documented in CDSL flow | LOW | 8 |
139+
140+
## Prioritized Recommendations
141+
142+
### Fix Now (CRITICAL)
143+
144+
| # | Recommendation | Findings | Files | Effort |
145+
|---|---------------|----------|-------|--------|
146+
| 1 | Rename `cpt-cypilot-feature-blueprint-system``kit-management` globally | D-03, D-04, Q-11 | `DECOMPOSITION.md`, `kit-management.md`, `agent-integration.md`, `version-config.md`, `v2-v3-migration.md` | S |
147+
| 2 | Fix ADR-0013 filename to match ID slug | Q-14 | `architecture/ADR/0013-cpt-cypilot-adr-extract-sdlc-kit-to-github-v1.md` → rename | S |
148+
| 3 | Add "Implementation Modules" section to `v2-v3-migration.md` | Q-10 | `architecture/features/v2-v3-migration.md` | S |
149+
| 4 | Reconcile kit-management flow/algo checkbox mismatch | Q-11 | `architecture/features/kit-management.md` | S |
150+
| 5 | Extract implementation details from PRD FRs to DESIGN | Q-01, Q-02 | `architecture/PRD.md` | M |
151+
| 6 | Reframe "single-layer generic engine" as product concept | Q-03 | `architecture/PRD.md` §1.1 | S |
152+
153+
### Fix Soon (HIGH)
154+
155+
| # | Recommendation | Findings | Files | Effort |
156+
|---|---------------|----------|-------|--------|
157+
| 7 | Propagate ADR-0001 to CLISPEC: remove `generate-resources`, deprecate `kit migrate`, fix `update` description | D-01, D-02 | `skills/cypilot/cypilot.clispec` | S |
158+
| 8 | Add `agents` command and proxy flags to CLISPEC | D-05, D-06 | `skills/cypilot/cypilot.clispec` | S |
159+
| 9 | Add `cypilot` console entry point | A-03 | `pyproject.toml` | S |
160+
| 10 | Update ADR-0013 and ADR-0014 status to `accepted` | D-12, D-13 | `architecture/ADR/0013-*.md`, `architecture/ADR/0014-*.md` | S |
161+
| 11 | Add ADRs 0013/0014 to DESIGN Section 5 traceability list | T-06 | `architecture/DESIGN.md` §5 | S |
162+
| 12 | Add acceptance criteria for remaining 15 FRs in PRD | T-07 | `architecture/PRD.md` §9 | M |
163+
| 13 | Implement `kit move-config` command (p1 FR scope) | A-04 | `skills/cypilot/scripts/cypilot/commands/` | M |
164+
| 14 | Add checkbox markers to ~20 CDSL steps in `agent-integration.md` + `developer-experience.md` | Q-13 | `architecture/features/agent-integration.md`, `developer-experience.md` | S |
165+
| 15 | Add risk documentation to ADR-0001 and ADR-0009 consequences | Q-15 | `architecture/ADR/0001-*.md`, `architecture/ADR/0009-*.md` | S |
166+
167+
### Improve Later (MEDIUM/LOW)
168+
169+
| # | Recommendation | Findings | Files | Effort |
170+
|---|---------------|----------|-------|--------|
171+
| 16 | Add `fr-core-toc` to F8 "Requirements Covered" in DECOMPOSITION | T-01 | `architecture/DECOMPOSITION.md` §2.8 | S |
172+
| 17 | Fix DECOMP F12 component ref: `workflow-engine``component-agent-generator` | D-10 | `architecture/DECOMPOSITION.md` §2.12 | S |
173+
| 18 | Update DECOMPOSITION status indicators (3 features show ⏳ but are checked) | Q-12 | `architecture/DECOMPOSITION.md` | S |
174+
| 19 | Add system context diagram to DESIGN | Q-08 | `architecture/DESIGN.md` §1.1 | M |
175+
| 20 | Document module/package structure mapping in DESIGN | Q-09 | `architecture/DESIGN.md` | M |
176+
| 21 | Use canonical `cpt-*` IDs in ADR traceability sections | Q-16 | `architecture/ADR/0006-*.md`, `0009-*.md`, `0012-*.md` | S |
177+
| 22 | Update PRD checkboxes for implemented FRs still marked `[ ]` | D-14 | `architecture/PRD.md` | S |
178+
| 23 | Expand acronyms on first use in PRD | Q-07 | `architecture/PRD.md` | S |
179+
| 24 | Mark unimplemented p2/p3 commands as `planned` in DESIGN §3.3 | A-05 | `architecture/DESIGN.md` §3.3 | S |
180+
| 25 | Clean stale blueprint docstrings in `toc.py` | D-09 | `skills/cypilot/scripts/cypilot/utils/toc.py` | S |
181+
| 26 | Move VS Code Plugin detailed behaviors from PRD to FEATURE spec | Q-06 | `architecture/PRD.md`, new FEATURE spec | M |
182+
| 27 | Capture ADR-0004 dual-mode and ADR-0012 marker format in DESIGN | A-01, A-02 | `architecture/DESIGN.md` | S |
183+
184+
## Phase Completion Log
185+
186+
| Phase | Title | Status | Issues |
187+
|-------|-------|--------|--------|
188+
| 1 | PRD ↔ DESIGN Cross-Reference | PASS | 6 (0C, 2H, 2M, 2L) |
189+
| 2 | DESIGN ↔ DECOMPOSITION ↔ FEATURE Chain | PASS | 8 (0C, 3H, 3M, 2L) |
190+
| 3 | ADR ↔ DESIGN Consistency | PASS | 6 (0C, 2H, 2M, 2L) |
191+
| 4 | PRD Quality Review | PASS | 9 (3C, 3H, 3M, 0L) |
192+
| 5 | DESIGN Quality Review | PASS | 7 (0C, 0H, 2M, 5L) |
193+
| 6 | DECOMPOSITION + FEATURE Quality Review | PASS | 20 (2C, 8H, 7M, 3L) |
194+
| 7 | ADR Batch Quality Review | PASS | 13 (1C, 4H, 5M, 3L) |
195+
| 8 | Proxy Codebase vs Specs | PASS | 12 (0C, 3H, 1M, 8L) |
196+
| 9 | Skill Engine vs Specs | PASS | 4 (0C, 0H, 2M, 2L) |
197+
| 10 | Specs vs Codebase Gap Analysis | PASS | 9 (0C, 4H, 2M, 3L) |
198+
| 11 | Consolidated Audit Report | PASS ||
199+
| **Total** | | **ALL PASS** | **94 raw (6C, 29H, 29M, 30L)** |
200+
201+
---
202+
203+
*Report generated as part of the `analyze-full-audit-cypilot` execution plan. Phase findings are stored in `.bootstrap/.plans/analyze-full-audit-cypilot/out/`.*

.bootstrap/.core/architecture/DECOMPOSITION.md

Lines changed: 61 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -17,6 +17,7 @@
1717
- [2.9 Advanced SDLC Workflows (EXTRACTED) ⏳ LOW](#29-advanced-sdlc-workflows-extracted--low)
1818
- [2.10 V2 → V3 Migration ⏳ HIGH](#210-v2--v3-migration--high)
1919
- [2.11 Spec Coverage ⏳ HIGH](#211-spec-coverage--high)
20+
- [2.12 Execution Plans ✅ HIGH](#212-execution-plans--high)
2021
- [3. Feature Dependencies](#3-feature-dependencies)
2122

2223
<!-- /toc -->
@@ -543,6 +544,63 @@ Cypilot DESIGN is decomposed into features organized around architectural layers
543544
- Registered codebase entries from `{cypilot_path}/config/artifacts.toml`
544545

545546

547+
### 2.12 [Execution Plans](features/execution-plans.md) ✅ HIGH
548+
549+
- [x] `p1` - **ID**: `cpt-cypilot-feature-execution-plans`
550+
551+
- **Purpose**: Decompose large agent tasks into self-contained phase files that fit within a single LLM context window, eliminating context overflow and non-deterministic results from attention drift.
552+
553+
- **Depends On**: `cpt-cypilot-feature-agent-integration`
554+
555+
- **Scope**:
556+
- Plan workflow (`workflows/plan.md`): instructions for AI agents to decompose tasks into phases and generate self-contained phase files
557+
- Phase file template (`requirements/plan-template.md`): strict structure for generated phase files — TOML frontmatter, inlined rules, pre-resolved paths, binary acceptance criteria
558+
- Decomposition strategies (`requirements/plan-decomposition.md`): how to split tasks by type — generate (template sections), analyze (checklist categories), implement (CDSL blocks)
559+
- Budget enforcement: ≤500 lines target, ≤1000 lines max per phase file
560+
- Plan storage: `{cypilot_path}/.plans/{task-slug}/` directory (git-ignored) with `plan.toml` manifest and phase files
561+
- Phase execution: agent reads self-contained phase file, follows instructions, reports against acceptance criteria
562+
- Status tracking: `plan.toml` tracks phase lifecycle (pending → in_progress → done/failed)
563+
564+
- **Out of scope**:
565+
- CLI commands for plan management (pure prompt-level feature)
566+
- Modifications to existing generate.md or analyze.md workflows
567+
- Deterministic validation of phase files (phase files are ephemeral execution artifacts)
568+
569+
- **Requirements Covered**:
570+
571+
- `p1` - `cpt-cypilot-fr-core-execution-plans`
572+
- `p1` - `cpt-cypilot-fr-core-workflows`
573+
574+
- **Design Principles Covered**:
575+
576+
- `p1` - `cpt-cypilot-principle-determinism-first`
577+
- `p1` - `cpt-cypilot-principle-occams-razor`
578+
579+
- **Design Constraints Covered**:
580+
581+
- `p1` - `cpt-cypilot-constraint-markdown-contract`
582+
583+
- **Domain Model Entities**:
584+
- ExecutionPlan
585+
- Phase
586+
- PhaseFile
587+
588+
- **Design Components**:
589+
590+
Components reused from Feature 5 (`workflow-engine` via generate/analyze patterns)
591+
592+
- **API**:
593+
None (prompt-level feature — no CLI commands)
594+
595+
- **Sequences**:
596+
597+
None (agent-driven workflow)
598+
599+
- **Data**:
600+
- `{cypilot_path}/.plans/{task-slug}/plan.toml` — plan manifest with phase metadata and status
601+
- `{cypilot_path}/.plans/{task-slug}/phase-{NN}-{slug}.md` — self-contained phase files
602+
603+
546604
---
547605

548606
## 3. Feature Dependencies
@@ -553,6 +611,8 @@ cpt-cypilot-feature-core-infra
553611
├─→ cpt-cypilot-feature-blueprint-system (Kit Management)
554612
555613
├─→ cpt-cypilot-feature-agent-integration
614+
│ ↓
615+
│ └─→ cpt-cypilot-feature-execution-plans
556616
557617
├─→ cpt-cypilot-feature-version-config
558618
@@ -574,6 +634,7 @@ cpt-cypilot-feature-core-infra
574634

575635
- `cpt-cypilot-feature-traceability-validation` requires `cpt-cypilot-feature-core-infra`: validator needs config manager for system/artifact resolution
576636
- `cpt-cypilot-feature-agent-integration` requires `cpt-cypilot-feature-core-infra`: agent generator consumes kit SKILL.md and workflow files
637+
- `cpt-cypilot-feature-execution-plans` requires `cpt-cypilot-feature-agent-integration`: plan workflow builds on existing generate/analyze workflows and agent entry points
577638
- `cpt-cypilot-feature-version-config` requires `cpt-cypilot-feature-core-infra`: update command needs config migration
578639
- `cpt-cypilot-feature-developer-experience` requires `cpt-cypilot-feature-traceability-validation`: VS Code plugin and doctor delegate to validator and traceability engine
579640
- `cpt-cypilot-feature-v2-v3-migration` requires `cpt-cypilot-feature-core-infra` and `cpt-cypilot-feature-traceability-validation`: migration needs v3 infrastructure and validation to verify completeness

0 commit comments

Comments
 (0)