Skip to content

chore(agents): ecosystem consistency pass to v1.2.2#5

Merged
jkyberneees merged 1 commit into
mainfrom
chore/agent-consistency-pass
Jun 3, 2026
Merged

chore(agents): ecosystem consistency pass to v1.2.2#5
jkyberneees merged 1 commit into
mainfrom
chore/agent-consistency-pass

Conversation

@jkyberneees
Copy link
Copy Markdown
Contributor

Summary

A systematic consistency and quality pass across all 22 agent definitions, the template spec (TEMPLATE.md), the README.md, and the landing page (docs/). Each finding from the agents/ review is addressed below, plus a new automated lint guard so this drift can't silently return.

A new make lint-agents target validates every agent on each preflight run.

Findings addressed

# Finding Fix
1 Missing webfetch: permission Declared explicitly in performance-optimizer & accessibility-expert (every agent now declares it)
2/3 3-layer version drift (H1 vs footer vs README) Unified the entire ecosystem on 1.2.2
4 Missing ## Limitations sections Added to 11 agents; gave research a real agent-level section (previously only an in-template one inside a code block)
5 Duplicated TS linter config in tester De-duplicated; kept the full PHASE 4 appendix and cross-referenced it
6 No guard against future drift Added tests/check_agents.sh + make lint-agents, wired into test-preflight; rewrote README §13 to enforce single-ecosystem-version
8 Only 4 Core Principles in fast-track agents Added a 5th ("know your limits / escalate") to doc-fixer & quick-reviewer
9 Non-standard escalation headings Renamed to the spec's "When to Escalate"
10 Unscoped write: true in research/fact-check Documented the single-report write-scoping convention as a frontmatter comment
11 SLA tables read as hard guarantees Clarified in TEMPLATE.md that timings/SLAs are typical targets, not guarantees
12 Duplicate version-history dates in TEMPLATE.md Fixed 1.0 → 2026-02-10 (confirmed via git history), added a 1.2.2 row, aligned the doc's own H1/footer

Landing page & README

  • docs/intro.html: page title and installer-demo terminal bumped to v1.2.2.
  • README.md: header version → 1.2.2, installer examples → v1.2.2, §13 rewritten.
  • The team grid and "20+ specialized agents" copy were already accurate (20 listed subagents + kai + engineering-team = 22) — left as-is.

Deferred (won't-fix, with rationale)

Trimming the inline boilerplate in docs/devops — it's valuable reference material for those agents, not a defect.

Verification

$ make lint-agents
[INFO] Ecosystem version (from README): 1.2.2
[PASS] All agent definitions are consistent (22 files).

🤖 Generated with Claude Code

Systematic consistency/quality pass across all 22 agent definitions, the
template spec, the README, and the landing page. Addresses every finding
from the agents/ review:

1. webfetch — declare explicit `webfetch:` permission in every agent
   (performance-optimizer and accessibility-expert were missing it).
2/3. version — unify the whole ecosystem on a single version (1.2.2).
   Fixes 3-layer drift: agent H1 headers (many said v1.0) vs. footers
   (1.2.0/1.0.0) vs. README header (1.2.1) vs. README §13 (1.2.0).
4. Limitations — add a `## Limitations` section to every agent that
   lacked one (architect, developer, devops, docs, engineering-team,
   reviewer, tester, fact-check, executive-summarizer, jira-writer, kai)
   and give research a real agent-level section (it previously only had
   an in-template "Gaps & Limitations" inside a code block).
5. tester — de-duplicate the TypeScript linter-config section; keep the
   full PHASE 4 appendix and cross-reference it from Best Practices.
6. lint guard — add tests/check_agents.sh (deny-list completeness,
   webfetch declared, footer/H1 version == README, Limitations present);
   wire it into `make lint-agents` / `test-preflight`. README §13
   rewritten to make single-ecosystem-version enforcement explicit.
8. doc-fixer & quick-reviewer — add a 5th Core Principle ("know your
   limits / escalate").
9. doc-fixer & quick-reviewer — rename non-standard escalation headings
   to the spec's "When to Escalate".
10. research & fact-check — document the write-scoping convention
    (single REPORT_/VERDICT_ report file) as a frontmatter comment.
11. TEMPLATE — clarify that Performance-Targets timings/SLAs are typical
    targets, not hard guarantees.
12. TEMPLATE — fix duplicate version-history dates (1.0 → 2026-02-10,
    confirmed from git history), add a 1.2.2 row, and align the doc's
    own H1/footer versions.

Landing page (docs/intro.html) and README installer examples bumped to
1.2.2; the team grid and "20+ agents" copy were already accurate.

Deferred (won't-fix, with rationale): trimming inline boilerplate in
docs/devops — it is valuable reference material, not a defect.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@jkyberneees jkyberneees merged commit b5bc570 into main Jun 3, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant