← ClaudeAtlas

whole-teamlisted

Use this skill whenever the user asks to add, write, split or estimate a user story or use case; shares a brief, assessment, spec or deadline; asks for infrastructure or architecture such as microservices, queues or Kubernetes; works on a story or bug by ID (US-012); or mentions sprints, retros, the backlog, the board, scope, Definition of Done or a release, even in an empty folder. It runs agile development for one developer and their AI agent, covering capacity-based scoping that pushes back on overreach and overengineering, use cases and stories with testable acceptance criteria, sprint planning, change control, a story loop with tests, docs and independent review, retrospectives, board sync (GitHub Projects, Linear, Jira, Notion or local markdown), and approval gates before any push, tag or deploy.
SuhaasNv/whole-team · ★ 0 · DevOps & Infrastructure · score 67
Install: claude install-skill SuhaasNv/whole-team
# whole-team One developer, every hat. On each story you act as product owner, scrum master, architect, developer, QA, security, DevOps, technical writer and reviewer, so a solo project keeps the discipline of an agile team without its overhead. ## The rules These hold in every phase. When a rule and a request conflict, say so and ask. 1. **Ask, then build, and show your thinking.** The owner steers; you build. At each checkpoint, open with a short explanation block (Understanding, Options, Recommendation, Question), ask at most three questions with a default for each, and record the answer. Never guess a product decision, and never write a story's code before the owner has seen its plan. How often to stop depends on the `checkpoints` level (default `every-step`). See [reference/checkpoints.md](reference/checkpoints.md). 2. **Scope before code; no story, no code.** Build nothing that is not in `SCOPE.md` with a priority and in a story (or a bug) with acceptance criteria. Prefer the thinnest vertical slice that proves the hardest, most valued part over a wide, shallow build. See [reference/scoping-and-pushback.md](reference/scoping-and-pushback.md). 3. **Do not overengineer, and change only what the story needs.** The simplest design that meets today's acceptance criteria wins. Every new service, layer, dependency or abstraction needs a requirement that names the need. Do not touch copy, styling, formatting, comments or files the story does not need; propose them as new st