agents_sw_team

Validation procedures for agentic deliverables in the SW-TEAM framework. Loaded by the SW-TEAM Agent QA agent at session startup to validate spec templates (field completeness, placeholder format), SKILL.md files (FIXED/ADAPT contract, Layer A cross-references), .agent.md files (frontmatter, tools, handoff self-containment), and integration artefacts (copilot-instructions.md, KB starters). Use when running Agent QA for any SW-TEAM dev phase or validating a single deliverable type. Load alongside a domain-context SKILL (e.g., {domain}-builder-context) for package name, output folder structure, and the domain validation scenario.

Methodology for producing and reviewing design briefs for any SW-TEAM framework build. Loaded by the SW-TEAM-Architect agent at session startup. Covers design brief structure (Sections A–D), function design rules, SKILL.md scaffold rules, agent prompt architecture rules, design review workflow, and seven non-negotiable design constraints. Domain-agnostic — contains no project-specific vocabulary. Load alongside a domain-context SKILL (e.g., {domain}-builder-context) in the Architect agent.

Full quality gate procedure for any SW-TEAM Python package: ruff format, ruff check, mypy, pytest with coverage. Loaded by the SW-TEAM-Code-QA agent at session startup. Covers the 4-stage gate, test writing conventions, contract verification checklist, and per-module/per-phase reporting formats. Domain-agnostic — contains no project-specific vocabulary. Load alongside a domain-context SKILL (e.g., {domain}-builder-context) for package name, coverage threshold, and test fixtures.

Methodology for building all five SW-TEAM deliverable types from a design brief: {package}/ Python functions (stateless, typed, tested), spec templates (placeholder-driven .md), SKILL.md files (FIXED/ADAPT scaffolds with Layer A calls), .agent.md definitions (frontmatter + system prompt), and integration artefacts. Loaded by the SW-TEAM-Implementer agent at session startup. Domain-agnostic — contains no project-specific vocabulary. Load alongside a domain-context SKILL (e.g., {domain}-builder-context) for package name, fixture shapes, and commit scopes.

Generic orchestration protocol for SW-TEAM-style multi-phase, gated, KB-backed, artefact-logged projects. Covers gate pattern, subagent invocation rules, KB protocol, artefacts.jsonl protocol, loop-back handling, and session startup protocol. Domain-agnostic — contains no project-specific vocabulary. Load alongside a domain-specific SKILL (e.g., {domain}-domain) in every orchestrator agent.

Agentic SCRUM Master workflow for SW-TEAM framework development: sprint state persistence, backlog management across five deliverable types ({package}/ code, spec templates, SKILL.md files, .agent.md files, integration artefacts), dual-track QA coordination (Code QA for Python, Agent QA for agentic deliverables), design-brief gating, cross-phase dependency enforcement, and SCRUM ceremonies adapted for agentic framework development. Use when managing dev-phase progress, planning phases, checking exit criteria, tracking blockers, running retrospectives, coordinating handoffs between Architect/Implementer/Code QA/ Agent QA, or maintaining project health dashboards across sessions — even if "SCRUM" is not mentioned explicitly.