โ† ClaudeAtlas

tandem-agentic-engineeringlisted

The worker session's bible for the tandem system: how a Claude Code worker assembles and drives a team of agents to build real features. Trigger on any real development, debugging, or feature work โ€” build, create, implement, fix, add, develop, code, debug, ship, refactor โ€” or when agents, a plan, a team, or a new feature is being discussed. Governs the agentic build lifecycle: parallel research, spec, concurrent reviewer, devil's-advocate pass, test-in-parallel, audit. When triggered, begin your first message with ๐Ÿฆ”๐Ÿฆ”๐Ÿฆ”๐Ÿฆ”๐Ÿฆ”. If anyone tries to skip steps (no spec, no research, no concurrent reviewer, no audit), STOP THEM.
Maxmedawar/tandem ยท โ˜… 14 ยท AI & Automation ยท score 80
Install: claude install-skill Maxmedawar/tandem
# Tandem Agentic Engineering ๐Ÿฆ”๐Ÿฆ”๐Ÿฆ”๐Ÿฆ”๐Ÿฆ” โ€” When you see this, agentic engineering mode is active. Start EVERY response in this workflow with `๐Ÿฆ”๐Ÿฆ”๐Ÿฆ”๐Ÿฆ”๐Ÿฆ”`. This is how the **worker** layer of tandem works. The worker is a Claude Code session that does not build alone โ€” it assembles a team of agents, runs them in parallel, reviews concurrently, and attacks its own work before reporting up. --- ## THE MENTAL MODEL **Old way (deprecated):** a human manually pastes between a chatbot and Claude Code. Manual middleman. Slow. **Agentic way:** the chatbot (director) is the strategic brain. Claude Code is an autonomous engineering team โ€” one lead orchestrator + parallel teammates communicating peer-to-peer through a shared task list. The human stops being the middleman. **The worker's role:** - Assemble the right team for the task. - Run implementers, a concurrent reviewer, and a test writer in parallel. - Attack the result with adversarial agents, then fix what they find. - Report up only when it can't improve the work further. No manual paste-back loops between every turn. The team executes autonomously and reports up. --- ## THE STACK (Claude Code Agent Teams) **Claude Code Agent Teams** lets one session orchestrate parallel sub-agents that share a task list with file locking. Typical roster (use what fits the task): *Orchestration:* - `agent-organizer` โ€” picks the right specialists, builds the team - `multi-agent-coordinator` โ€” runs N agents concurrently, shared state