agile-projectlisted

Use this skill whenever you are working on a Go project following this agile workflow — features in .features/, sprints in .sprints/, ADRs in .adrs/, global architecture in .architecture/, per-feature ARCHITECTURE.md written by the Architect, tasks under .features/<slug>/tasks/ with scaffolding-first plus red/green triples (TASK.md shared + TASK-red.md + TASK-green.md), spec isolation between paired teammates, dispute arbitration by the sprint-planner, complexity-based agent assignment (scaffolder, red-opus/sonnet/haiku, green-opus/sonnet/haiku, e2e-tester, reviewer), PM and Architect roles for feature definition, and retro-driven sub-sprints for private-helper test coverage. Triggers: mention of sprint planning, feature breakdown, TASK.md / TASK-red.md / TASK-green.md / SCAFFOLD.md, SPRINT.md, REVIEW.md, RETRO.md, Definition of Ready, Definition of Done, blockers, questions, ADRs with revisit flag, dispute files in .disputes/, any of the sprint-planner/product-manager/architect/scaffolder/red-*/green-*/revie
JLugagne/claude-skills · ★ 0 · AI & Automation · score 72

Install: claude install-skill JLugagne/claude-skills

# Agile Project Workflow Workflow for Go projects using strict TDD, sprint-based agile, complexity-graded agents running as Claude Code teammates, scaffolding-first contracts, and spec isolation between paired teammates. --- # Go file editing — ABSOLUTE RULE **STRICTLY FORBIDDEN** to use `Edit`, `Write`, `Read`, or any generic tool to read or modify a `.go` file. For **every** `.go` file without exception: - Reading → `go-surgeon symbol` or `go-surgeon overview` - Creation → `go-surgeon create` - Modification → `go-surgeon patch_function`, `patch_struct`, `patch_interface`, `update`, `insert_call`, etc. This rule applies even for a single-line change. No exceptions. --- # Parallelization — ABSOLUTE RULE Use **sub-agents** (`Agent` tool) or **agent teams** (`CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS`) for any task composed of independent parts (no file conflicts, no result dependencies). - Launch parallel work in a single message (multiple simultaneous tool calls, or a team spawn). - Never execute sequentially what can be parallelized. - Examples: scaffolding multiple features in parallel, writing independent tests, creating files in different packages. ## Parallelism granularity Maximum theoretical fan-out (e.g., "23 independent red tasks") is rarely the right unit. Rate limits, token budgets, and the cost of recovering from concurrent crashes (see *Agent crash recovery*) make wide fan-outs fragile. **Default heuristic — feature as the unit of parallelism:** - One a