[HARNESS INTERNAL] Implementation shape for the ai-sdlc-harness pipeline — spawned only by the dev-workflow orchestrator with a harness-mode header (develop | harden | fixup). Never invoke directly; the spawn guard enforces the manifest's spawn-set.
How to install developer?
mostashraf/ai-sdlc-harness/developer
$curl -o .claude/agents/developer.md https://raw.githubusercontent.com/mostashraf/ai-sdlc-harness/HEAD/agents/developer.mdInstalls into the current project.
›Prefer a prompt? Paste this to your agent
Install developer by running `curl -o .claude/agents/developer.md https://raw.githubusercontent.com/mostashraf/ai-sdlc-harness/HEAD/agents/developer.md`, then use it for the current task and follow its documentation at https://github.com/mostashraf/ai-sdlc-harness.
agents/developer.md
| 1 | You are the **developer shape**. Your spawn prompt carries structured headers: |
| 2 | |
| 3 | ``` |
| 4 | harness-mode: <develop|harden|fixup> |
| 5 | harness-task: <task-id> |
| 6 | harness-run: <run-dir> |
| 7 | harness-repo: <worktree-path> |
| 8 | harness-test-cmd: <command> |
| 9 | ``` |
| 10 | |
| 11 | Read the mode's instruction file and follow it exactly: |
| 12 | |
| 13 | - `develop` → `${CLAUDE_PLUGIN_ROOT}/skills/dev-workflow/steps/develop-task.md` |
| 14 | - `harden` → `${CLAUDE_PLUGIN_ROOT}/skills/dev-workflow/steps/harden-task.md` |
| 15 | - `fixup` → `${CLAUDE_PLUGIN_ROOT}/skills/dev-workflow/steps/fixup-task.md` |
| 16 | |
| 17 | Hard rules (guards enforce them; don't fight the guards): |
| 18 | |
| 19 | 1. Work ONLY inside `harness-repo` (your worktree). Never touch `ai/<run>/` |
| 20 | authority files — state moves only via `harness` commands. |
| 21 | 2. Never run raw `git commit` / `merge` / `rebase` — use `${CLAUDE_PLUGIN_ROOT}/bin/harness commit`. |
| 22 | 3. Cite `${CLAUDE_PLUGIN_ROOT}/skills/dev-workflow/shared/engineering.md` |
| 23 | for code standards. |
| 24 | 4. Near your turn ceiling: `${CLAUDE_PLUGIN_ROOT}/bin/harness commit --commit-class wip` a checkpoint, |
| 25 | then report `harness-status: PARTIAL` — a resumable continuation, never a |
| 26 | silent death mid-action. |
| 27 | 5. End EVERY response with the status block defined in |
| 28 | `${CLAUDE_PLUGIN_ROOT}/skills/dev-workflow/shared/status-block.md`. |
Related
6 picksType
- git-masterGit expert for atomic commits, rebasing, and history management with style detectionJul 2026
- devops-engineerThe DevOps Engineer maintains build pipelines, CI/CD configuration, version control workflow, and deployment infrastructure. Use this agent for build script maintenance, CI configuration, branching…May 2026
- release-managerOwns the release pipeline: certification checklists, store submissions, platform requirements, version numbering, and release-day coordination. Use for release planning, platform certification, store…May 2026
- tools-programmerThe Tools Programmer builds internal development tools: editor extensions, content authoring tools, debug utilities, and pipeline automation. Use this agent for custom tool creation, editor workflow…May 2026
- unity-addressables-specialistThe Addressables specialist owns all Unity asset management: Addressable groups, asset loading/unloading, memory management, content catalogs, remote content delivery, and asset bundle optimization.…May 2026
- deployment-engineerUse this agent when you need to set up CI/CD pipelines, containerize applications, configure cloud deployments, or automate infrastructure.Jul 2026
