agents-templated 2.2.14 → 2.2.16
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.
- package/README.md +36 -0
- package/package.json +1 -1
- package/templates/CLAUDE.md +43 -20
package/README.md
CHANGED
|
@@ -32,6 +32,17 @@ Agents Templated is a project governance and agent-orchestration scaffold.
|
|
|
32
32
|
- It installs rule modules in `.claude/rules/` for security, testing, planning, workflows, and guardrails.
|
|
33
33
|
- It includes `validate`, `doctor`, `update`, and `workflow` commands to keep scaffolds healthy over time.
|
|
34
34
|
|
|
35
|
+
## Orchestration-First Workflow (Current Model)
|
|
36
|
+
|
|
37
|
+
The current model is orchestration-first: give one objective and let the CLI generate a deterministic multi-phase specialist handoff.
|
|
38
|
+
|
|
39
|
+
- Use `agents-templated orchestrate "<objective>"` to run end-to-end routing.
|
|
40
|
+
- Subagent selection is automatic and policy-driven from `CLAUDE.md`.
|
|
41
|
+
- Mode-locked specialists require explicit mode handling (`qa-specialist`, `performance-specialist`).
|
|
42
|
+
- Security escalation is conditionally mandatory based on trigger conditions.
|
|
43
|
+
- Deprecated specialist aliases are redirected to canonical agents with explicit notices.
|
|
44
|
+
- Orchestration stops on blocked/failed phases and returns structured stop conditions.
|
|
45
|
+
|
|
35
46
|
What it is not:
|
|
36
47
|
|
|
37
48
|
- Not a framework generator.
|
|
@@ -51,6 +62,7 @@ npx agents-templated@latest wizard
|
|
|
51
62
|
```bash
|
|
52
63
|
agents-templated workflow
|
|
53
64
|
agents-templated problem-map "daily briefing assistant for founders"
|
|
65
|
+
agents-templated orchestrate "build auth API and admin dashboard"
|
|
54
66
|
```
|
|
55
67
|
|
|
56
68
|
### 3. Optional preset bootstrap
|
|
@@ -111,6 +123,7 @@ Your AI assistant will auto-load the configurations and follow enterprise patter
|
|
|
111
123
|
| **Interactive Wizard** | Guided setup with personalized recommendations |
|
|
112
124
|
| **AI Agents Supported** | Cursor, GitHub Copilot, Claude, and generic agents via `AGENTS.MD` |
|
|
113
125
|
| **Deterministic Commands** | Slash-command contracts with strict structured outputs |
|
|
126
|
+
| **Automatic Orchestration** | Objective-to-specialist auto-routing via `orchestrate` with deterministic phase outputs |
|
|
114
127
|
| **Intent-Routing Ready** | Command schema supports `slash-command-auto` mode for agent-side routing policies |
|
|
115
128
|
| **Security-First** | OWASP Top 10 protection patterns built-in |
|
|
116
129
|
| **Hardening Workflow** | Risk-based hardening rules plus verification/release gates |
|
|
@@ -238,6 +251,7 @@ agents-templated list
|
|
|
238
251
|
|
|
239
252
|
# Lifecycle workflow and specialist commands
|
|
240
253
|
agents-templated workflow
|
|
254
|
+
agents-templated orchestrate "build auth API and dashboard"
|
|
241
255
|
```
|
|
242
256
|
|
|
243
257
|
### Workflow Commands
|
|
@@ -260,6 +274,28 @@ These commands provide deterministic specialist guidance aligned to the sprint l
|
|
|
260
274
|
|
|
261
275
|
Each command maps to deterministic contract files in `.claude/commands/` and uses the schema in `.claude/commands/SCHEMA.md`.
|
|
262
276
|
|
|
277
|
+
### Automatic Orchestration Command
|
|
278
|
+
|
|
279
|
+
Use orchestration when you want the system to chain specialists automatically from one objective.
|
|
280
|
+
|
|
281
|
+
```bash
|
|
282
|
+
# Human-readable orchestration summary
|
|
283
|
+
agents-templated orchestrate "build auth API and dashboard"
|
|
284
|
+
|
|
285
|
+
# Structured output for pipelines and automation
|
|
286
|
+
agents-templated orchestrate "prepare production deployment" --json
|
|
287
|
+
|
|
288
|
+
# Force a specific scenario
|
|
289
|
+
agents-templated orchestrate "ship release candidate" --scenario deployment --json
|
|
290
|
+
```
|
|
291
|
+
|
|
292
|
+
Orchestration behavior:
|
|
293
|
+
|
|
294
|
+
- Uses deterministic routing and phase sequencing.
|
|
295
|
+
- Enforces mode-lock constraints for `qa-specialist` and `performance-specialist`.
|
|
296
|
+
- Includes deprecation notices when legacy aliases are routed.
|
|
297
|
+
- Emits structured stop conditions if a phase is blocked or fails.
|
|
298
|
+
|
|
263
299
|
### Deprecated Workflow Aliases
|
|
264
300
|
|
|
265
301
|
The CLI keeps selected legacy names as non-breaking redirects with deterministic notices.
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "agents-templated",
|
|
3
|
-
"version": "2.2.
|
|
3
|
+
"version": "2.2.16",
|
|
4
4
|
"description": "Technology-agnostic development template with multi-AI agent support (Cursor, Copilot, VSCode, Gemini), security-first patterns, and comprehensive testing guidelines",
|
|
5
5
|
"main": "index.js",
|
|
6
6
|
"bin": {
|
package/templates/CLAUDE.md
CHANGED
|
@@ -50,28 +50,51 @@ Skills add capability only. They must not override security, testing, or core co
|
|
|
50
50
|
|
|
51
51
|
| Subagent | Path | Invoke when... |
|
|
52
52
|
|----------|------|----------------|
|
|
53
|
-
| planner | `.claude/agents/planner.md` | Breaking down features into phased plans |
|
|
53
|
+
| planner | `.claude/agents/planner.md` | Breaking down features into phased execution plans |
|
|
54
54
|
| architect | `.claude/agents/architect.md` | System design decisions, ADRs, trade-off analysis |
|
|
55
|
-
|
|
|
56
|
-
|
|
|
57
|
-
| security-reviewer | `.claude/agents/security-reviewer.md` | Scanning for security vulnerabilities |
|
|
58
|
-
| build-error-resolver | `.claude/agents/build-error-resolver.md` | Fixing build and type errors |
|
|
59
|
-
| e2e-runner | `.claude/agents/e2e-runner.md` | Running Playwright E2E test suites |
|
|
60
|
-
| refactor-cleaner | `.claude/agents/refactor-cleaner.md` | Removing dead code and unused dependencies |
|
|
61
|
-
| doc-updater | `.claude/agents/doc-updater.md` | Syncing docs and READMEs after code changes |
|
|
62
|
-
| performance-profiler | `.claude/agents/performance-profiler.md` | Diagnosing latency, CPU, memory, and build bottlenecks |
|
|
63
|
-
| performance-specialist | `.claude/agents/performance-specialist.md` | Diagnosing bottlenecks or validating performance thresholds with explicit mode |
|
|
64
|
-
| test-data-builder | `.claude/agents/test-data-builder.md` | Building deterministic fixtures, seeds, and mock datasets for downstream validation |
|
|
65
|
-
| dependency-auditor | `.claude/agents/dependency-auditor.md` | Auditing package risk, CVEs, and upgrade hygiene |
|
|
66
|
-
| configuration-validator | `.claude/agents/configuration-validator.md` | Validating env settings, defaults, and deploy readiness |
|
|
55
|
+
| backend-specialist | `.claude/agents/backend-specialist.md` | Implementing backend features, APIs, and server-side logic |
|
|
56
|
+
| frontend-specialist | `.claude/agents/frontend-specialist.md` | Implementing UI, interaction, accessibility, and client-side state |
|
|
67
57
|
| database-migrator | `.claude/agents/database-migrator.md` | Planning safe migrations with validation and rollback gates |
|
|
68
|
-
|
|
|
69
|
-
|
|
|
70
|
-
|
|
|
71
|
-
|
|
|
72
|
-
|
|
|
73
|
-
|
|
|
74
|
-
|
|
|
58
|
+
| deployment-specialist | `.claude/agents/deployment-specialist.md` | Deployment planning, config validation, rollout, and rollback |
|
|
59
|
+
| performance-specialist | `.claude/agents/performance-specialist.md` | Bottleneck diagnosis (mode=profile) or load threshold validation (mode=load) |
|
|
60
|
+
| qa-specialist | `.claude/agents/qa-specialist.md` | Pre-implementation test planning (mode=design) or post-implementation validation (mode=validation) |
|
|
61
|
+
| e2e-runner | `.claude/agents/e2e-runner.md` | Running end-to-end test suites and reporting flakiness |
|
|
62
|
+
| code-reviewer | `.claude/agents/code-reviewer.md` | Reviewing code for quality, correctness, and severity prioritization |
|
|
63
|
+
| security-reviewer | `.claude/agents/security-reviewer.md` | Security risk gating — invoke when authn/authz, secrets, or new public endpoints are touched |
|
|
64
|
+
| refactor-cleaner | `.claude/agents/refactor-cleaner.md` | Removing dead code and unused dependencies in approved cleanup windows |
|
|
65
|
+
| build-error-resolver | `.claude/agents/build-error-resolver.md` | Fixing compile, type, lint, and import failures only |
|
|
66
|
+
| compatibility-checker | `.claude/agents/compatibility-checker.md` | API contract compatibility and breaking-change verdicts |
|
|
67
|
+
| dependency-auditor | `.claude/agents/dependency-auditor.md` | Auditing package risk, CVEs, and upgrade hygiene |
|
|
68
|
+
| doc-updater | `.claude/agents/doc-updater.md` | Syncing docs and READMEs after accepted behavior changes |
|
|
69
|
+
| test-data-builder | `.claude/agents/test-data-builder.md` | Building deterministic fixtures, seeds, and mock datasets |
|
|
70
|
+
|
|
71
|
+
### Subagent Auto-Routing Rules
|
|
72
|
+
|
|
73
|
+
When a task is received, automatically select and invoke the appropriate subagent(s) without waiting for explicit instruction. Follow these rules:
|
|
74
|
+
|
|
75
|
+
- Always read `.claude/agents/<name>.md` before invoking that subagent to confirm its contract.
|
|
76
|
+
- For multi-step tasks, chain subagents in dependency order — do not invoke all at once.
|
|
77
|
+
- qa-specialist MUST be invoked with explicit mode:
|
|
78
|
+
- mode=design for pre-implementation test planning
|
|
79
|
+
- mode=validation for post-implementation sign-off
|
|
80
|
+
- If mode is unclear, HALT and ask before proceeding.
|
|
81
|
+
- performance-specialist MUST be invoked with explicit mode:
|
|
82
|
+
- mode=profile for bottleneck diagnosis
|
|
83
|
+
- mode=load for threshold validation
|
|
84
|
+
- If mode is unclear, HALT and ask before proceeding.
|
|
85
|
+
- security-reviewer is mandatory when any of these are true:
|
|
86
|
+
- Authentication, authorization, or session logic is touched
|
|
87
|
+
- A new public endpoint is added
|
|
88
|
+
- Secrets, credentials, or environment variables are changed
|
|
89
|
+
- dependency-auditor reports a High or Critical finding
|
|
90
|
+
- deployment-specialist always runs internal phases in order:
|
|
91
|
+
release_readiness → config_validation → rollout_execution
|
|
92
|
+
Never skip or reorder phases.
|
|
93
|
+
- build-error-resolver handles compile/lint/type failures only.
|
|
94
|
+
Do not route feature or architecture decisions through it.
|
|
95
|
+
- refactor-cleaner max retry cap is 2 cycles. If build still fails after 2 cycles, HALT and escalate to the feature owner.
|
|
96
|
+
- Deprecated agent names (tdd-guide, load-tester, performance-profiler, release-ops-specialist, configuration-validator) must redirect to their canonical replacements with a deprecation warning.
|
|
97
|
+
Never invoke deprecated agents directly.
|
|
75
98
|
|
|
76
99
|
Subagents are bounded agents with limited tool access. They inherit all policy from this file and may not override security, testing, or core constraints.
|
|
77
100
|
|