Added canonical schema reference to 7 implementation/specialist agents that produce Standards Compliance Reports:
- backend-engineer-golang
- backend-engineer-typescript
- devops-engineer
- frontend-bff-engineer-typescript
- frontend-engineer
- qa-analyst
- sre
Each now references docs/AGENT_DESIGN.md as the canonical source for output schema requirements per Content Duplication Prevention rule.
Note: prompt-quality-reviewer already documents its Standards Compliance Report section as 'Not Applicable' since it's an analyst agent.
Generated-by: Claude
AI-Model: claude-sonnet-4-5-20250929
Added reference to dev-team/docs/standards/devops.md as canonical source to prevent duplication per Content Duplication Prevention rule.
Generated-by: Claude
AI-Model: claude-sonnet-4-5-20250929
- Refactor all 7 dev-team agents to reference standards via WebFetch
- Remove duplicated Domain Standards sections from agents
- Update golang.md to lib-commons v3 with correct logging pattern:
- commons/zap for logger initialization (bootstrap/config only)
- commons/log for Logger interface (services, routes, consumers)
- Add Standards Compliance Output Format section to golang.md
- Add Standards Loading sections to qa-analyst and frontend-engineer agents
Agents now contain only: role definition, output schema, expertise
knowledge, blockers, and WebFetch references to standards files.
Generated-by: Claude
AI-Model: claude-opus-4-5-20251101
Removes the required_when field from agent output_schema definitions
as it was not implemented in any orchestrator validation layer. The
conditional requirement for Standards Compliance is already enforced
through prose instructions in each agent's documentation section
'Standards Compliance Report (MANDATORY when invoked from dev-refactor)'.
Updated description to clarify enforcement is via prose instructions.
Generated-by: Claude
AI-Model: claude-opus-4-5-20251101
Adds conditional Standards Compliance output section to all dev-team agents. When invoked from dev-refactor skill, agents compare codebase against Lerian/Ring standards (lib-commons for Go, lib-commons-js for TypeScript) and produce compliance reports.
Changes:
- Add Standards Compliance to output_schema with required_when conditional
- Add comparison categories and output format documentation per agent
- Update dev-refactor prompt templates to request compliance reports
- Categories adapted per domain (Go: lib-commons, TS: lib-commons-js, SRE: health/logging/tracing only)
Generated-by: Claude
AI-Model: claude-opus-4-5-20251101
- Add 'What If No PROJECT_RULES.md Exists?' HARD BLOCK section to all 7 agents
- Add 'What If Non-Compliant?' and 'Cannot Be Overridden' sections to devops, sre, qa agents
- Remove ~230 lines of internal duplications across all agents
- Consolidate Standards Loading references to single source of truth
- Merge redundant Blocker Format templates
- Unify Handling Ambiguous Requirements with cross-references
Generated-by: Claude
AI-Model: claude-opus-4-5-20251101
- Remove frontend-engineer.md agent (consolidated into frontend-bff-engineer-typescript)
- Fix dev-cycle state file inconsistency (cycle-state.json -> current-cycle.json)
- Update all cross-references in 19 files to point to frontend-bff-engineer-typescript
- Update agent count from 8 to 7 in documentation
Generated-by: Claude
AI-Model: claude-opus-4-5-20251101
Changed from passive code block format to explicit action instruction:
- Added table with url and prompt parameters
- Clear 'MANDATORY ACTION: You MUST use the WebFetch tool NOW'
- Explicit 'Execute this WebFetch before proceeding' instruction
- Blocker instruction if WebFetch fails
Previous format was just text, not an actionable directive.
Generated-by: Claude
AI-Model: claude-opus-4-5-20251101
Consistent format in all agents:
1. `docs/PROJECT_RULES.md` (local project) - If exists, follow it EXACTLY
2. Ring Standards via WebFetch (Step 2 above) - ALWAYS REQUIRED
3. Both are necessary and complementary - no override
**Both Required:** PROJECT_RULES.md (local project) + Ring Standards (via WebFetch)
Generated-by: Claude
AI-Model: claude-opus-4-5-20251101
All agents now use:
- PROJECT_RULES.md (local project) for project-specific standards
- Ring Standards via WebFetch from GitHub (always required)
Both are necessary and complementary - no override. Removed all references to local docs/standards/* files that could cause confusion.
Generated-by: Claude
AI-Model: claude-opus-4-5-20251101
- Add mandatory Standards Loading section to 5 agents (golang, typescript, devops, frontend, sre)
- Agents now WebFetch Ring standards from GitHub raw URLs
- Both PROJECT_RULES.md (local) and Ring standards (remote) are HARD GATES
- Fix using-dev-team agent count (9→7), remove non-existent agents
- Add Blocker Criteria section to dev-feedback-loop
- Standardize qa-analyst output_schema to Implementation archetype
Generated-by: Claude
AI-Model: claude-opus-4-5-20251101
Remove language-agnostic generic agents in favor of the specialized language-specific variants. This simplifies agent selection by eliminating ambiguity when choosing between generic and specialized versions.
Deleted agents:
- backend-engineer.md (use backend-engineer-golang or backend-engineer-typescript)
- frontend-engineer.md (use frontend-engineer-typescript)
Updated all documentation and cross-references across 19 files to reflect the change from 9 to 7 developer agents.
Generated-by: Claude
AI-Model: claude-opus-4-5-20251101
Add 'Project Standards Integration' section and clarify that docs/STANDARDS.md and docs/standards/devops.md references are for the user's project, not the ring repository. Aligns with pattern used in backend-engineer-golang.md.
Generated-by: Claude
AI-Model: claude-opus-4-5-20251101
Major changes to the development cycle:
- Add Gate 2 (dev-sre) for observability validation (metrics, health checks, logging)
- Update to 6-gate cycle: implementation→devops→SRE→testing→review→validation
- Embed language/domain standards directly into all 10 agents
- Create dev-sre skill with full observability requirements
- Create sre.md standards document
- Rename skills: development-cycle→dev-cycle, dev-devops-setup→dev-devops
- Add dev-analysis skill for codebase analysis against STANDARDS.md
- Add dev-refactor command for standards-based refactoring workflow
- Bump ring-dev-team version to 0.5.0
Generated-by: Claude
AI-Model: claude-opus-4-5-20251101
docs(commands): add detailed documentation for core workflows
fix(scripts): improve argument and file path handling in shell
refactor(hooks): use jq for robust JSON escaping in session-start hook
fix(docs): correct gate numbering in pre-dev feature documentation
feat(dev-team): expand developer agents to 10 with language specialists
feat(ralph-wiggum): add plugin for iterative development loops via Stop hook
docs: overhaul all documentation for new plugin organization
fix(hooks): ignore symlinks in claude-md-reminder script
chore(deps): pin PyYAML version and update plugin installs in hooks
2025-11-26 15:05:24 -03:00
Renamed from developers/agents/devops-engineer.md (Browse further)
