devflow-kit 3.2.0 → 3.3.0

package/src/assets/skills/consistency/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: consistency
-description: This skill should be used when reviewing code for naming convention violations, pattern deviations, or inconsistent API styles.
+description: This skill should be used when reviewing code for naming or pattern inconsistencies.
 user-invocable: false
 allowed-tools: Read, Grep, Glob
 ---

package/src/assets/skills/database/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: database
-description: This skill should be used when reviewing database queries, migrations, indexes, or schema changes.
+description: This skill should be used when reviewing queries, migrations or schema changes.
 user-invocable: false
 allowed-tools: Read, Grep, Glob
 ---

package/src/assets/skills/dependencies/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: dependencies
-description: This skill should be used when reviewing dependency changes, lock files, or package additions.
+description: This skill should be used when reviewing dependency or lock file changes.
 user-invocable: false
 allowed-tools: Read, Grep, Glob
 ---

package/src/assets/skills/dependency-research/SKILL.md

@@ -1,9 +1,6 @@
 ---
 name: dependency-research
-description: >-
-  This skill should be used when the user asks to "add a utility", "create a helper",
-  "implement parsing", "build a wrapper", or writes infrastructure/utility code that
-  may already exist as a well-maintained package. Enforces research before building.
+description: This skill should be used when the user asks to "add a utility", "create a helper", "build a wrapper", or writes utility code a maintained package may already provide.
 user-invocable: false
 allowed-tools: Read, Grep, Glob
 ---
@@ -54,9 +51,9 @@ Nice-to-haves: {optional features}
 
 ### Phase 2: Search
 
-Delegate research to an Explore subagent to keep main session context clean.
+Spawn an Explore subagent when you can spawn agents, to keep main session context clean; otherwise search directly, using the template's questions as your checklist.
 
-**Spawn an Explore agent** with this prompt template:
+**Prompt template** for the Explore agent:
 
 ```
 Agent(subagent_type="Explore"):

package/src/assets/skills/design-review/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: design-review
-description: This skill should be used when reviewing implementation plans for anti-patterns, checking design quality before implementation, or performing plan-level quality assessment. Provides 6 anti-pattern detection rules for the Design agent and inline planning.
+description: This skill should be used when reviewing implementation plans for anti-patterns.
 user-invocable: false
 allowed-tools: Read, Grep, Glob
 ---

package/src/assets/skills/docs-framework/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: docs-framework
-description: This skill should be used when the user asks to "create a review report", "write a status log", "add documentation", "name this artifact", or creates files in the .devflow/docs/ directory. Provides naming conventions, templates, and directory structure for reviews, debug sessions, design docs, and all persistent Devflow documentation artifacts.
+description: This skill should be used when creating files in the .devflow/docs/ directory.
 user-invocable: false
 allowed-tools: Read, Bash, Glob
 ---

package/src/assets/skills/documentation/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: documentation
-description: This skill should be used when reviewing for documentation drift, missing API docs, or stale comments.
+description: This skill should be used when reviewing for documentation drift or stale comments.
 user-invocable: false
 allowed-tools: Read, Grep, Glob
 ---

package/src/assets/skills/gap-analysis/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: gap-analysis
-description: This skill should be used when analyzing design documents, specifications, or plans for completeness gaps, architectural issues, security concerns, and performance implications. Provides focus-specific detection patterns for the Design agent.
+description: This skill should be used when analyzing specs or plans for completeness gaps.
 user-invocable: false
 allowed-tools: Read, Grep, Glob
 ---

package/src/assets/skills/git/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: git
-description: This skill should be used when the user asks to "commit changes", "create a pull request", "rebase safely", "manage branches", "fix merge conflicts", "undo a commit", "comment on a PR", "create a release", or performs any git/GitHub operations. Provides safety patterns, atomic commit formatting, PR descriptions, sensitive file detection, and GitHub API usage.
+description: This skill should be used when the user asks to "commit changes", "create a pull request", "rebase safely", or performs any git/GitHub operation.
 user-invocable: false
 allowed-tools: Bash, Read, Grep, Glob
 ---

package/src/assets/skills/go/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: go
-description: This skill should be used when the user works with Go files (.go), asks about "error handling", "interfaces", "goroutines", "channels", "packages", or discusses Go idioms and concurrency. Provides patterns for error handling, interface design, concurrency, and package organization.
+description: This skill should be used when the user works with Go files (.go), asks about "error handling", "interfaces", "goroutines", or discusses Go idioms and concurrency.
 user-invocable: false
 allowed-tools: Read, Grep, Glob
 activation:

package/src/assets/skills/java/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: java
-description: This skill should be used when the user works with Java files (.java), asks about "records", "sealed classes", "Optional", "streams", "composition over inheritance", or discusses modern Java patterns and API design. Provides patterns for type system usage, error handling, immutability, and concurrency.
+description: This skill should be used when the user works with Java files (.java), asks about "records", "sealed classes", "streams", or discusses modern Java patterns.
 user-invocable: false
 allowed-tools: Read, Grep, Glob
 activation:

package/src/assets/skills/patterns/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: patterns
-description: This skill should be used when the user asks to "create an API endpoint", "add CRUD operations", "implement event handlers", "set up logging", "add configuration", or builds features involving database operations, REST/GraphQL APIs, pub/sub patterns, or service configuration. Provides implementation patterns that follow existing codebase conventions.
+description: This skill should be used when the user asks to "create an API endpoint", "add CRUD operations", "implement event handlers", "set up logging", or adds database operations, REST/GraphQL APIs, pub/sub.
 user-invocable: false
 allowed-tools: Read, Grep, Glob
 ---

package/src/assets/skills/performance/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: performance
-description: This skill should be used when reviewing code for N+1 queries, memory leaks, or I/O bottlenecks.
+description: This skill should be used when reviewing code for N+1 queries or memory leaks.
 user-invocable: false
 allowed-tools: Read, Grep, Glob
 ---

package/src/assets/skills/python/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: python
-description: This skill should be used when the user works with Python files (.py), asks about "type hints", "protocols", "dataclasses", "async/await", "decorators", or discusses Pythonic patterns and data modeling. Provides patterns for type safety, error handling, data modeling, and async programming.
+description: This skill should be used when the user works with Python files (.py), asks about "type hints", "protocols", "dataclasses", "async/await", or discusses Pythonic patterns.
 user-invocable: false
 allowed-tools: Read, Grep, Glob
 activation:

package/src/assets/skills/qa/SKILL.md

@@ -1,8 +1,6 @@
 ---
 name: qa
-description: This skill should be used when performing scenario-based acceptance testing,
-  designing QA test plans, or validating that implementation behavior matches acceptance
-  criteria beyond unit tests.
+description: This skill should be used when designing or running scenario-based acceptance tests.
 user-invocable: false
 allowed-tools: Read, Grep, Glob, Bash
 ---

package/src/assets/skills/quality-gates/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: quality-gates
-description: This skill should be used when evaluating implementation quality before submission, checking correctness, security, and simplicity.
+description: This skill should be used when evaluating implementation quality before submission.
 user-invocable: false
 allowed-tools: Read, Grep, Glob, Edit, Write, Bash
 ---
@@ -26,7 +26,7 @@ Based on [Google Engineering Practices](https://google.github.io/eng-practices/r
 |----------|--------|---------|
 | **P0** | MUST fix | Design, Functionality, Security |
 | **P1** | SHOULD fix | Complexity, Error Handling, Tests |
-| **P2** | FIX if time | Naming, Consistency, Documentation |
+| **P2** | FIX if straightforward | Documentation (Naming and Consistency belong to the Simplify agent: report them as SKIP) |
 
 ### P0 - Design
 Does the implementation fit the architecture? Follows existing patterns, respects layer boundaries, dependencies injected.
@@ -48,11 +48,8 @@ Errors handled explicitly? No swallowed exceptions, helpful messages, resources
 ### P1 - Tests
 New code tested? Covers happy path, errors, edges. Tests behavior, not implementation.
 
-### P2 - Naming
-Names clear and descriptive? No cryptic abbreviations, consistent style.
-
-### P2 - Consistency
-Matches existing patterns? Same style, same conventions, no unnecessary divergence.
+### P2 - Naming and Consistency
+Owned by the Simplify agent, which applies the project's naming and style standards. Report both as SKIP; do not judge or fix them here.
 
 ### P2 - Documentation
 Will others understand? Complex logic commented, public APIs documented, no outdated comments.
@@ -99,7 +96,7 @@ Check Design, Functionality, Security. If issues found and fixable, fix immediat
 Check Complexity, Error Handling, Tests. Fix issues found.
 
 ### Step 4: Evaluate P2 Pillars
-Check Naming, Consistency, Documentation. Fix if time permits.
+Check Documentation and fix it if straightforward. Naming and Consistency are the Simplify agent's: SKIP.
 
 ### Step 5: Generate Report
 Document status of each pillar, fixes applied, and overall readiness.
@@ -122,13 +119,13 @@ Document status of each pillar, fixes applied, and overall readiness.
 - Tests: PASS/FIXED
 
 ### P2 Pillars
-- Naming: PASS/FIXED/SKIP
-- Consistency: PASS/FIXED/SKIP
-- Documentation: PASS/FIXED/SKIP
+- Naming: SKIP (Simplify agent)
+- Consistency: SKIP (Simplify agent)
+- Documentation: PASS/FIXED
 
 ### Summary
 Issues Found: {n}, Fixed: {n}
-Status: READY / BLOCKED
+Status: PASS / FIXED / BLOCKED
 ```
 
 ---

package/src/assets/skills/quality-gates/references/report-template.md

@@ -44,13 +44,13 @@ Use this template when generating your self-review report.
 
 ---
 
-### P2 Pillars (FIX if Time Permits)
+### P2 Pillars (Documentation only)
 
 | Pillar | Status | Notes |
 |--------|--------|-------|
-| Naming | PASS/FIXED/SKIP | {details} |
-| Consistency | PASS/FIXED/SKIP | {details} |
-| Documentation | PASS/FIXED/SKIP | {details} |
+| Naming | SKIP | Simplify agent |
+| Consistency | SKIP | Simplify agent |
+| Documentation | PASS/FIXED | {details if fixed} |
 
 **Fixes Applied** (if any):
 - {file:line} - {what was fixed}
@@ -61,7 +61,7 @@ Use this template when generating your self-review report.
 
 **Issues Found**: {total count}
 **Issues Fixed**: {count}
-**Status**: READY / BLOCKED
+**Status**: PASS / FIXED / BLOCKED
 
 {If BLOCKED, explain what cannot be fixed and why}
 ```
@@ -105,12 +105,12 @@ Add user profile update endpoint
 
 ---
 
-### P2 Pillars (FIX if Time Permits)
+### P2 Pillars (Documentation only)
 
 | Pillar | Status | Notes |
 |--------|--------|-------|
-| Naming | PASS | Clear, descriptive names |
-| Consistency | PASS | Matches existing patterns |
+| Naming | SKIP | Simplify agent |
+| Consistency | SKIP | Simplify agent |
 | Documentation | PASS | JSDoc on public methods |
 
 ---
@@ -119,7 +119,7 @@ Add user profile update endpoint
 
 **Issues Found**: 0
 **Issues Fixed**: 0
-**Status**: READY
+**Status**: PASS
 ```
 
 ### Example 2: Issues Fixed
@@ -165,12 +165,12 @@ Implement order cancellation flow
 
 ---
 
-### P2 Pillars (FIX if Time Permits)
+### P2 Pillars (Documentation only)
 
 | Pillar | Status | Notes |
 |--------|--------|-------|
-| Naming | PASS | Clear names |
-| Consistency | PASS | Matches existing order methods |
+| Naming | SKIP | Simplify agent |
+| Consistency | SKIP | Simplify agent |
 | Documentation | FIXED | Added JSDoc explaining cancellation rules |
 
 **Fixes Applied**:
@@ -182,7 +182,7 @@ Implement order cancellation flow
 
 **Issues Found**: 5
 **Issues Fixed**: 5
-**Status**: READY
+**Status**: FIXED
 ```
 
 ### Example 3: Blocked
@@ -233,12 +233,12 @@ before implementing refund feature.
 
 ## Status Definitions
 
-| Status | Meaning |
-|--------|---------|
-| PASS | No issues found for this pillar |
-| FIXED | Issue found and resolved |
-| SKIP | P2 only - issue noted but not fixed due to time |
-| BLOCKED | Cannot fix - requires escalation |
+| Status | Pillar | Overall (`### Status`) |
+|--------|--------|------------------------|
+| PASS | No issues found for this pillar | No change was needed |
+| FIXED | Issue found and resolved | Fixes were committed and every P0 and P1 is fixed |
+| SKIP | Naming and Consistency only - owned by the Simplify agent | - |
+| BLOCKED | Cannot fix - requires escalation | A P0 cannot be fixed in scope |
 
 ---
 
@@ -247,7 +247,7 @@ before implementing refund feature.
 Before submitting report:
 - [ ] All P0 pillars are PASS or FIXED
 - [ ] All P1 pillars are PASS or FIXED
-- [ ] P2 pillars evaluated (PASS/FIXED/SKIP)
+- [ ] Documentation evaluated (PASS/FIXED); Naming and Consistency reported as SKIP
 - [ ] All fixes documented with file:line
 - [ ] Summary accurately reflects status
 - [ ] If BLOCKED, clear explanation provided

package/src/assets/skills/react/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: react
-description: This skill should be used when the user works with React components (.tsx/.jsx), asks about "hooks", "state management", "context providers", "memo optimization", "useEffect", or discusses component composition and rendering performance. Provides patterns for hooks, state, effects, memoization, and React-specific architecture.
+description: This skill should be used when the user works with React components (.tsx/.jsx), asks about "hooks", "state management", "memo optimization", or discusses component composition.
 user-invocable: false
 allowed-tools: Read, Grep, Glob
 activation:

package/src/assets/skills/regression/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: regression
-description: This skill should be used when reviewing changes that may remove exports, change signatures, or alter behavior.
+description: This skill should be used when reviewing changes that may break existing behavior.
 user-invocable: false
 allowed-tools: Read, Grep, Glob
 ---

package/src/assets/skills/reliability/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: reliability
-description: This skill should be used when reviewing code for unbounded loops, missing assertions, excessive allocation, or deep indirection.
+description: This skill should be used when reviewing code for unbounded loops or missing assertions.
 user-invocable: false
 allowed-tools: Read, Grep, Glob
 ---

package/src/assets/skills/research-codebase/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: research-codebase
-description: Local codebase research — find patterns, trace flows, map dependencies without browsing the web
+description: Local codebase research — find patterns, trace flows, map dependencies
 user-invocable: false
 allowed-tools: Read, Grep, Glob
 ---

package/src/assets/skills/research-competitor/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: research-competitor
-description: Competitor analysis — structured feature comparison, positioning analysis, and gap identification
+description: Competitor analysis — feature comparison, positioning and gap identification
 user-invocable: false
 allowed-tools: WebSearch, WebFetch
 ---

package/src/assets/skills/research-external/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: research-external
-description: External web research — find documentation, articles, and community knowledge with untrusted-data discipline
+description: External web research — docs, articles, community knowledge; untrusted data
 user-invocable: false
 allowed-tools: WebSearch, WebFetch
 ---

package/src/assets/skills/research-technology/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: research-technology
-description: Technology evaluation — assess libraries, frameworks, and tools against project requirements
+description: Technology evaluation — assess libraries, frameworks and tools against requirements
 user-invocable: false
 allowed-tools: WebSearch, WebFetch, Read
 ---

package/src/assets/skills/review-methodology/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: review-methodology
-description: This skill should be used when performing a code review to apply the standard 6-step review process.
+description: This skill should be used when performing a code review (the 6-step process).
 user-invocable: false
 allowed-tools: Read, Grep, Glob, Bash
 ---

package/src/assets/skills/rust/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: rust
-description: This skill should be used when the user works with Rust files (.rs), asks about "ownership", "borrowing", "lifetimes", "Result/Option", "traits", or discusses memory safety and type-driven design. Provides patterns for ownership, error handling, type system usage, and safe concurrency.
+description: This skill should be used when the user works with Rust files (.rs), asks about "ownership", "borrowing", "lifetimes", "traits", or discusses memory safety.
 user-invocable: false
 allowed-tools: Read, Grep, Glob
 activation:

package/src/assets/skills/security/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: security
-description: This skill should be used when reviewing code for injection flaws, auth bypasses, or hardcoded secrets.
+description: This skill should be used when reviewing code for injection, auth or secrets flaws.
 user-invocable: false
 allowed-tools: Read, Grep, Glob
 ---

package/src/assets/skills/software-design/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: software-design
-description: This skill should be used when the user asks to "handle errors", "inject dependencies", "return Result", "make it immutable", "compose with pipes", or implements business logic, error handling, or service composition. Provides Result type patterns, dependency injection, immutability by default, pipe composition, and structured logging for robust application architecture.
+description: This skill should be used when the user asks to "handle errors", "inject dependencies", "return Result", "make it immutable", or implements business logic or error handling.
 user-invocable: false
 allowed-tools: Read, Grep, Glob, AskUserQuestion
 ---

package/src/assets/skills/test-driven-development/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: test-driven-development
-description: This skill should be used when implementing new features, fixing bugs, or writing new code. Enforces RED-GREEN-REFACTOR.
+description: This skill should be used when implementing features or fixing bugs. Enforces RED-GREEN-REFACTOR.
 user-invocable: false
 allowed-tools: Read, Grep, Glob
 activation:
@@ -62,12 +62,11 @@ Don't optimize. Don't refactor. Don't clean up. Just pass the test.
 
 ### Step 3: REFACTOR — Improve Without Changing Behavior
 
-Now clean up. Extract helpers, rename variables, simplify logic. Tests stay green throughout.
+Now clean up: extract helpers, rename, simplify, apply DRY. Tests stay green throughout.
 
 ```
 Run the affected tests after every refactoring step.
 If a test breaks during refactor, undo immediately — you changed behavior.
-Apply DRY, extract patterns, improve readability.
 ```
 
 **Checkpoint:** All affected tests still pass. Code is clean. Repeat from Step 1 for next behavior.
@@ -98,11 +97,10 @@ These are the excuses developers use to skip TDD. Recognize and reject them.
 | "I'll write tests after" | Need to see the shape first | Tests ARE the shape — they define the interface before implementation exists | Write the test first |
 | "Too simple to test" | It's just a getter/setter | Getters break, defaults change, edge cases hide in "simple" code | Write it — takes 30 seconds |
 | "I'll refactor later" | Just get it working now | "Later" never comes; technical debt compounds silently | Refactor now in Step 3 |
-| "Test is too hard to write" | Setup is complex, mocking is painful | Hard-to-test code = bad design; the test is telling you the interface is wrong | Simplify the interface first |
-| "Need to see the whole picture" | Can't test what I haven't designed yet | TDD IS design; each test reveals the next piece of the interface | Let the test guide the design |
+| "Test is too hard to write" or "the test setup is too complex" | Mocking is painful | Hard-to-test code = bad design, and complex setup = too much coupling; the test is telling you the interface is wrong | Simplify the interface first |
+| "Need to see the whole picture" or "the architecture first" | Can't test what I haven't designed or structured yet | TDD IS design; each test reveals the next piece of the interface, and tests DEFINE the architecture | Let the tests drive the design and structure |
 | "Tests slow me down" | Faster to just write the code | Faster until the first regression; TDD is faster for anything > 50 lines | Trust the cycle |
 | "Framework is hard to set up" | Setup is complex | One-time cost vs recurring regression cost; untested code compounds debt | Set up the framework first — that IS the work |
-| "Need the architecture first" | Can't test without structure | Tests DEFINE the architecture; they reveal what interfaces are needed | Let tests drive the structure |
 | "This is infrastructure, not logic" | Plumbing doesn't need tests | Infrastructure carries data; broken plumbing floods everything downstream | Test the contract, not the internals |
 | "Deadline is tight, no time for tests" | Ship now, test later | Untested code ships bugs; fixing bugs under deadline is slower than TDD | TDD is faster under pressure, not slower |
 
@@ -110,13 +108,11 @@ See `references/rationalization-prevention.md` for extended examples with code.
 
 ### Red Flags — STOP Immediately
 
-The rationalization table above catches excuses you make *before starting*. These red flags catch you *mid-work* — thoughts that signal you are about to skip a step.
+The table above catches excuses *before starting*. These catch you *mid-work*: thoughts that signal you are about to skip a step.
 
 | Thought | Correction |
 |---------|------------|
 | "Let me write the implementation first, tests after" | Delete the code. Write the test. Watch it fail. Then rewrite. |
-| "I need to see the shape before I can test" | The test IS the shape. It defines the interface before implementation. |
-| "The test setup is too complex for this" | Complex setup = too much coupling. Simplify the design first. |
 | "I'll just spike this and add tests later" | Unless the user said "spike" — you're rationalizing, not prototyping. |
 | "Let me get it working, then lock it with tests" | Those tests verify your implementation, not the requirement. Backwards. |
 | "I know this works, I've written it before" | Past code passed past tests. This code needs its own failing test. |
@@ -124,20 +120,11 @@ The rationalization table above catches excuses you make *before starting*. Thes
 
 ### Test-First vs Code-First
 
-**Code-first** (wrong):
-1. Write `parseConfig()` — split lines, filter comments, build map
-2. Write test: `parseConfig("key=val")` passes
-3. Ship. Undiscovered: empty input, malformed lines, multi-value keys, whitespace
-> Test mirrors implementation. Edge cases stay hidden until production.
+**Code-first** (wrong): write `parseConfig()`, then a test that mirrors it (`parseConfig("key=val")` passes). Empty input, malformed lines, multi-value keys and whitespace stay hidden until production.
 
-**Test-first** (correct):
-1. Test: "ignores comment lines" — `parseConfig("# comment\nkey=val")` → `{key: val}`
-2. Test: "handles empty input" — `parseConfig("")` → empty result
-3. Test: "rejects malformed lines" — `parseConfig("no-equals")` → error
-4. Implement `parseConfig()` to satisfy all three
-> Tests define the contract. Implementation forced to handle edges from the start.
+**Test-first** (correct): "ignores comment lines", then "handles empty input", then "rejects malformed lines", each failing first and each driving the next slice of `parseConfig()`, so it handles the edges from the start.
 
-The difference: code-first tests verify what you *happened to build*. Test-first tests specify what *should exist*.
+Code-first tests verify what you *happened to build*. Test-first tests specify what *should exist*.
 
 ### When Stuck
 
@@ -153,14 +140,7 @@ The difference: code-first tests verify what you *happened to build*. Test-first
 
 ## Process Enforcement
 
-When implementing any feature under ambient IMPLEMENT:
-
-1. **Identify the first behavior** — What is the simplest thing this feature must do?
-2. **Write the test** — Describe that behavior as a failing test
-3. **Run the test** — Confirm it fails (RED)
-4. **Write minimum code** — Just enough to pass (GREEN)
-5. **Refactor** — Clean up while tests stay green (REFACTOR)
-6. **Repeat** — Next behavior, next test, next cycle
+When implementing any feature under ambient IMPLEMENT, start from the simplest thing it must do, take that one behavior through RED, GREEN and REFACTOR, then repeat for the next behavior.
 
 ### File Organization
 

package/src/assets/skills/testing/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: testing
-description: This skill should be used when the user asks to "write tests", "fix failing tests", "improve test coverage", "add integration tests", "debug a flaky test", or reviews test quality. Provides behavior-focused testing patterns, coverage analysis, and detection of brittle test anti-patterns like implementation coupling and non-deterministic assertions.
+description: This skill should be used when the user asks to "write tests", "fix failing tests", "improve test coverage" or "debug a flaky test", or reviews test quality.
 user-invocable: false
 allowed-tools: Read, Grep, Glob, AskUserQuestion
 activation:

package/src/assets/skills/typescript/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: typescript
-description: This skill should be used when the user works with TypeScript files (.ts/.tsx), asks about "generics", "type guards", "utility types", "strict typing", "discriminated unions", or discusses type safety and inference. Provides patterns for Result types, exhaustive checks, branded types, and type-safe API contracts.
+description: This skill should be used when the user works with TypeScript files (.ts/.tsx), asks about "generics", "type guards", "utility types", "discriminated unions", or discusses type safety.
 user-invocable: false
 allowed-tools: Read, Grep, Glob
 activation:

package/src/assets/skills/ui-design/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: ui-design
-description: This skill should be used when the user asks to "design a component", "pick colors", "improve typography", "fix spacing", "choose a layout", or discusses visual design, CSS, styling decisions, or responsive interfaces. Provides patterns for typography scales, color systems, spacing, and production-grade UI design.
+description: This skill should be used when the user asks to "design a component", "pick colors", "improve typography", "fix spacing", or discusses visual design and CSS.
 user-invocable: false
 allowed-tools: Read, Grep, Glob
 activation:

package/src/assets/skills/worktree-support/SKILL.md

@@ -7,8 +7,6 @@ allowed-tools: Bash, Read
 
 # Worktree Support
 
-Canonical patterns for worktree-aware agents and multi-worktree discovery in commands.
-
 ## Iron Law
 
 > **WORKTREE_PATH IS A PREFIX, NOT A FLAG**
@@ -16,8 +14,6 @@ Canonical patterns for worktree-aware agents and multi-worktree discovery in com
 > When WORKTREE_PATH is provided, it changes how you resolve ALL paths — git commands,
 > file reads, .devflow/docs/ paths. It's not a toggle; it's a coordinate system shift.
 
----
-
 ## Agent Path Resolution
 
 When `WORKTREE_PATH` is provided to an agent:
@@ -31,46 +27,6 @@ When `WORKTREE_PATH` is provided to an agent:
 
 If `WORKTREE_PATH` is omitted, behavior is unchanged (use cwd). This is the common case.
 
----
-
-## Worktree Discovery Algorithm (Commands)
-
-For commands that auto-discover worktrees (`/code-review`, `/resolve`):
-
-### Step 1: List Worktrees
-
-Run `git worktree list --porcelain`
-
-### Step 2: Parse Each Entry
-
-Extract: `worktree {path}`, `HEAD {sha}`, `branch refs/heads/{name}`
-
-### Step 3: Filter
-
-Exclude:
-- **Bare worktrees** (no branch)
-- **Detached HEAD** (no named branch; roots and detached HEAD: `references/roots.md`)
-- **Protected branches**: `main`, `master`, `develop`, `integration`, `trunk`, `release/*`, `staging`, `production`
-- **Mid-rebase or mid-merge**: check `git -C {path} status` for "rebase in progress" or "merging"
-
-### Step 4: Check for Work
-
-Each worktree must have commits ahead of base branch. Skip those that are clean/up-to-date.
-
-### Step 5: Deduplicate
-
-If two worktrees are on the same branch, use only the first worktree's path.
-
-### Step 6: Sort
-
-Sort by last commit date (most recent first).
-
-### Step 7: Return
-
-Return list of reviewable worktrees with path, branch, HEAD SHA.
-
----
-
 ## Protected Branches (Canonical List)
 
 `main`, `master`, `develop`, `integration`, `trunk`, `release/*`, `staging`, `production`
@@ -78,15 +34,7 @@ Return list of reviewable worktrees with path, branch, HEAD SHA.
 All components (agents, commands, skills) must use this exact list when checking for protected branches.
 The HUD mirrors this list in `TRUNK_BRANCHES`/`TRUNK_BRANCH_PREFIXES`/`isTrunkBranch()` in `src/core/git.ts` — update both together.
 
----
-
-## Multi-Worktree Mode
+## Extended References
 
-| Condition | Behavior |
-|-----------|----------|
-| 0 reviewable worktrees | Error: no reviewable branches found |
-| 1 worktree (common case) | Single-worktree flow, zero behavior change |
-| 2+ worktrees | Report count, process worktrees **sequentially** (one at a time) |
-| 5+ worktrees | Report count and proceed — user manages their worktree count |
-| `--path` flag provided | Use only that worktree, skip discovery |
-| Same branch in 2 worktrees | Deduplicate — review once using first worktree's path |
+- `references/discovery.md` — the 7-step discovery algorithm and multi-worktree mode
+- `references/roots.md` — project data roots and detached HEAD