developlisted

# Development Team Workflow Entry point for any implementation task (new feature, bug fix, refactor, or other code change) in a target project. Replaces plan mode and manual exploration. The workflow is orchestrated by the root session with four specialized agents. ## Preconditions This skill MUST be invoked from the **root Claude Code session**. Spawned subagents cannot spawn further agents, so nested invocation will fail. If you are already inside a subagent when the user asks for this flow, stop and instruct them to restart at the root session. ## Team composition | Role | Agent name | May write | Read-only | |---|---|---|---| | Analyst | `analyst` | — | yes | | Challenger | `challenger` | — | yes | | Developer | `developer` | production-code paths declared in `PROJECT_BRIEF.md` | | | QA | `qa` | test-code paths declared in `PROJECT_BRIEF.md` | | Role boundaries are derived from `PROJECT_BRIEF.md` in the target folder — not hardcoded. ## Step 1 — Resolve session and target folders 1. Run `pwd` via Bash to get `SESSION_DIR`. Do not hardcode this path; always resolve it fresh. 2. Ask the user for the target project folder (`TARGET_DIR`) as an absolute path. Derive a default suggestion by computing the parent of `SESSION_DIR` and appending a project-name placeholder: `<parent-of-SESSION_DIR>/<project-name>` (e.g., `/workspace/my-project` when `SESSION_DIR` is `/workspace/project-builder`). Present this default explicitly. Resolve relative paths with `cd <path> && pwd`