kodelyth-ecc 1.5.1 → 1.5.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -0,0 +1,74 @@
1
+ ---
2
+ description: Parallel founding-team blast for new projects. Fires architect + security + UX + TDD + pair-programmer simultaneously. One command, 5 specialist reports at once.
3
+ ---
4
+
5
+ # /project-launch — Parallel Founding Team
6
+
7
+ Launch all founding-team agents in parallel on your new project. What would take 40+ minutes sequentially finishes in under 10 minutes as one parallel burst.
8
+
9
+ ## Usage
10
+
11
+ ```
12
+ /project-launch <description>
13
+ /project-launch "SaaS dashboard with Stripe billing, user auth, real-time data"
14
+ /project-launch --full # adds performance-optimizer and api-guardian to the team
15
+ ```
16
+
17
+ ## What Gets Launched in Parallel
18
+
19
+ Five specialist agents fire simultaneously, each with the same project description:
20
+
21
+ | Agent | Deliverable |
22
+ |---|---|
23
+ | `architect` | System design — components, data flow, boundaries, trade-offs |
24
+ | `pair-programmer` | Approach validation — risks, wrong turns, questions to answer before coding |
25
+ | `security-reviewer` | Threat model — auth, data exposure, OWASP risks for THIS project type |
26
+ | `tdd-guide` | Test strategy — what to test first, test pyramid, critical paths |
27
+ | `ux-reviewer` | UX blueprint — user flows, accessibility requirements, interaction risks |
28
+
29
+ With `--full`, also adds:
30
+ - `performance-optimizer` — scaling bottlenecks, caching strategy, query patterns
31
+ - `api-guardian` — API contract design, versioning strategy, breaking change risks
32
+
33
+ ## How It Works
34
+
35
+ 1. Read the project description from `$ARGUMENTS`
36
+ 2. If no description provided, ask for one in one sentence
37
+ 3. Spawn all 5 (or 7) agents simultaneously with `run_in_background: true`
38
+ 4. Each agent receives: the project description + its specialist brief
39
+ 5. Wait for all to complete
40
+ 6. Aggregate results into a structured **Project Launch Report**:
41
+
42
+ ```
43
+ ## PROJECT LAUNCH REPORT
44
+ ### Architecture (architect)
45
+ [findings]
46
+
47
+ ### Approach Risks (pair-programmer)
48
+ [findings]
49
+
50
+ ### Threat Model (security-reviewer)
51
+ [findings]
52
+
53
+ ### Test Strategy (tdd-guide)
54
+ [findings]
55
+
56
+ ### UX Blueprint (ux-reviewer)
57
+ [findings]
58
+ ```
59
+
60
+ 7. After report: ask "Which area do you want to go deeper on first?"
61
+
62
+ ## Token Efficiency
63
+
64
+ Each agent gets a **narrow, focused context** — just the project description + its specialist instructions. No agent carries the full conversation history. The system prompt (rules + agents) is cached across all parallel agents. Result: 5× the analysis at roughly 2× the token cost of a single sequential session.
65
+
66
+ ## When to Use
67
+
68
+ - Starting any non-trivial project (3+ components, real users, production intent)
69
+ - Before writing a single line of code
70
+ - When you want to catch architecture mistakes before they're baked in
71
+
72
+ ## Arguments
73
+
74
+ $ARGUMENTS
@@ -0,0 +1,90 @@
1
+ ---
2
+ description: Parallel full-team audit for existing projects. Fires code-reviewer + security-reviewer + performance-optimizer + api-guardian simultaneously. One command, complete audit at once.
3
+ ---
4
+
5
+ # /team-review — Parallel Full-Team Audit
6
+
7
+ Run a full audit of your existing codebase with 4 specialist agents firing simultaneously. What would take an hour sequentially takes 15 minutes in parallel.
8
+
9
+ ## Usage
10
+
11
+ ```
12
+ /team-review # full audit — all 4 agents on entire codebase
13
+ /team-review src/auth/ # focus all agents on a specific directory
14
+ /team-review --changed # audit only files changed since last commit
15
+ /team-review --pre-release # adds release-captain for release readiness check
16
+ ```
17
+
18
+ ## What Gets Launched in Parallel
19
+
20
+ | Agent | Focus |
21
+ |---|---|
22
+ | `code-reviewer` | Quality, patterns, dead code, naming, complexity, maintainability |
23
+ | `security-reviewer` | OWASP Top 10, secrets, injection, auth gaps, CVEs in deps |
24
+ | `performance-optimizer` | N+1 queries, unbounded loops, missing indexes, memory leaks, bundle size |
25
+ | `api-guardian` | Breaking changes, missing validation, versioning gaps, contract drift |
26
+
27
+ With `--pre-release`, also adds:
28
+ - `release-captain` — release readiness: changelog, semver, rollback plan, smoke test coverage
29
+
30
+ ## How It Works
31
+
32
+ 1. Identify the target scope (whole repo, directory, or changed files)
33
+ 2. Spawn all 4 agents simultaneously with `run_in_background: true`
34
+ 3. Each agent scans its assigned concern independently
35
+ 4. Wait for all to complete
36
+ 5. Aggregate into a structured **Team Review Report**:
37
+
38
+ ```
39
+ ## TEAM REVIEW REPORT
40
+
41
+ ### Code Quality (code-reviewer)
42
+ CRITICAL: [list]
43
+ HIGH: [list]
44
+ MEDIUM: [list]
45
+
46
+ ### Security (security-reviewer)
47
+ CRITICAL: [list]
48
+ HIGH: [list]
49
+
50
+ ### Performance (performance-optimizer)
51
+ HIGH: [list]
52
+ MEDIUM: [list]
53
+
54
+ ### API Contracts (api-guardian)
55
+ BREAKING: [list]
56
+ WARN: [list]
57
+
58
+ ---
59
+ TOTAL: X critical, Y high, Z medium
60
+ RECOMMENDATION: [ship / fix critical first / block]
61
+ ```
62
+
63
+ 6. After report: "Which finding do you want to fix first?"
64
+
65
+ ## Severity Levels
66
+
67
+ | Level | Meaning | Action |
68
+ |---|---|---|
69
+ | CRITICAL | Security vulnerability, data loss, production breakage | Block — fix before merge |
70
+ | HIGH | Bug, broken contract, significant perf regression | Fix before shipping |
71
+ | MEDIUM | Maintainability debt, minor perf, code smell | Fix when convenient |
72
+ | LOW | Style, suggestion | Optional |
73
+
74
+ ## When to Use
75
+
76
+ - Before any major PR merge
77
+ - Pre-release audit
78
+ - Onboarding to an unfamiliar codebase (run `/team-review` to get the full picture fast)
79
+ - After a large refactor
80
+ - Monthly health check on long-running projects
81
+
82
+ ## Time and Token Efficiency
83
+
84
+ Sequential audit (4 agents one by one): ~40–60 minutes, full context per agent.
85
+ `/team-review` parallel: ~10–15 minutes, narrow focused context per agent.
86
+ System prompt cached across all agents → each pays 10% on that prefix.
87
+
88
+ ## Arguments
89
+
90
+ $ARGUMENTS
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "kodelyth-ecc",
3
- "version": "1.5.1",
3
+ "version": "1.5.3",
4
4
  "description": "Production-grade AI coding toolkit \u2014 61 agents, 188 skills, 80 commands, god-tier intent routing, local self-learning memory with auto chat detection, incident response, load testing. Works with Claude Code, Windsurf, Cursor, Codex, Antigravity, and OpenCode.",
5
5
  "author": "Kodelyth <github.com/sifxprime>",
6
6
  "license": "MIT",
@@ -24,7 +24,11 @@
24
24
  "auto-recall",
25
25
  "incident-response",
26
26
  "load-testing",
27
- "kodelyth"
27
+ "kodelyth",
28
+ "image-generation",
29
+ "parallel-agents",
30
+ "multi-agent",
31
+ "project-launch"
28
32
  ],
29
33
  "bin": {
30
34
  "kodelyth-ecc": "bin/kodelyth-ecc.js"