← ClaudeAtlas

autonomous-devlisted

Use to develop a feature or bug fix end-to-end through a TDD git-worktree workflow — interactively (developer-led) or unattended (autonomous-mode, driven by the dispatcher). Triggers on phrases like "implement issue #N", "fix this bug", "add a feature", "create a worktree", "write test cases", "push and open a PR", "check CI", "address review comments", "resolve review threads", "/q review", "/codex review", "implement this autonomously", or any partial step in the design → worktree → tests → implement → verify → review → PR → CI → E2E lifecycle. Interactive mode asks for decisions; autonomous mode makes decisions per autonomous-mode.md and posts progress comments to the GitHub issue.
zxkane/autonomous-dev-team · ★ 20 · AI & Automation · score 67
Install: claude install-skill zxkane/autonomous-dev-team
# TDD Development Workflow A complete development workflow enforcing test-driven development, git worktree isolation, code review, CI verification, and E2E testing. Works in two modes: interactive (default) for human-guided sessions, and autonomous for fully unattended GitHub issue implementation. > **NON-NEGOTIABLE RULES — every step marked MANDATORY is required.** Do not skip, defer, or ask the user whether to run these steps. Execute them automatically as part of the workflow. This covers creating PRs, waiting for CI, running E2E tests, and addressing reviewer findings. --- ## Mode Detection ### Interactive Mode (default) Used when a developer is present. The workflow: - Asks the user for design approval before proceeding to implementation - Presents design canvases and waits for feedback - Pauses at key decision points for user input - Reports final status and lets the user decide when to merge ### Autonomous Mode Triggered when running inside the `scripts/autonomous-dev.sh` wrapper. The workflow: - Makes all decisions autonomously (see "Decision Making Guidelines" below) - Posts progress comments to the GitHub issue instead of asking questions - Creates design docs but skips interactive approval - Stops after verification -- does not merge (the review agent handles that) - Marks requirement checkboxes in the issue body as work progresses --- ## Cross-Platform Notes This skill works across IDEs that support skills.sh. Map generic verbs in this doc to your IDE's