tandem-engineering-workflow

Solid

Engineering discipline for development work orchestrated through Tandem, regardless of whether the worker is Claude, Codex, or another supported engine. Trigger for implementation, debugging, review, test, or architecture work. Begin the first response with πŸ“‹πŸ“‹πŸ“‹πŸ“‹πŸ“‹ when active.

AI & Automation 25 stars 9 forks Updated 1 weeks ago MIT

Install

View on GitHub

Quality Score: 79/100

Stars 20%
47
Recency 20%
90
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Tandem engineering workflow πŸ“‹πŸ“‹πŸ“‹πŸ“‹πŸ“‹ The engineering workflow is active. This skill defines how an MCP-capable director should plan, delegate, verify, and report engineering work performed through Tandem. It is engine-neutral. Engine-specific features, such as Claude model controls or the Claude-only relay, are optional special cases. ## Roles - Human: sets the goal, grants authority, makes consequential product decisions. - Director: clarifies the outcome, selects devices and engines, assigns bounded work, and owns the final answer. - Worker session: implements or investigates one defined part of the goal. - Reviewer session: independently checks the result when the risk or scope warrants it. One session may hold several roles on a small task. Keep ownership explicit on larger work. ## Workflow ### Understand 1. Restate the concrete outcome and definition of done. 2. Inspect the repository, current branch, local instructions, and existing changes before editing. 3. Identify what is unknown and research only what affects the decision. 4. Push back on unsafe, contradictory, or needlessly broad requests with concrete reasons. ### Plan 5. Break work into phases with clear file ownership and tests. 6. Decide which assignments are independent and which depend on earlier output. 7. Select a device and engine based on advertised capability and data locality. Do not route by guesswork. 8. Use a planning mode when the chosen engine provides one and the work is non-trivia...

Details

Author
Maxmedawar
Repository
Maxmedawar/tandem
Created
2 months ago
Last Updated
1 weeks ago
Language
TypeScript
License
MIT

Similar Skills

Semantically similar based on skill content β€” not just same category

AI & Automation Solid

tandem-agentic-engineering

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.

25 Updated 1 weeks ago
Maxmedawar
AI & Automation Solid

tandem-orchestration

Operate Tandem as a multi-agent, multi-device MCP orchestrator. Use it when an MCP-capable caller needs to start, inspect, steer, interrupt, or coordinate Claude, Codex, shell, or Hermes sessions on the local hub or another enrolled device. Also covers the optional Claude-only relay. Begin the first response with πŸ—οΈπŸ—οΈπŸ—οΈπŸ—οΈπŸ—οΈ when this skill activates.

25 Updated 1 weeks ago
Maxmedawar
AI & Automation Listed

cto

DEFAULT ENTRY POINT for engineering work — building a feature, starting a new app or product, or fixing a bug end-to-end. Runs a gated idea→spec→build→review→QA→ship pipeline. Use for requests like "build X", "add feature Y", "new app for Z", or when work should end deployed and verified. For pure visual/design work use a design skill; for a one-off diff review use eng-review directly.

0 Updated 3 days ago
laltaffer