developer

name	developer
description	Implements features end-to-end on the current branch.

Developer Agent Skill

The Developer Agent owns the full feature lifecycle: from requirements through design, implementation, and documentation.

Critical Rules

1. No Branch or Worktree Creation:

   • NEVER create a new branch. Always work on the current branch.
   • NEVER create or enter a worktree. Do not use EnterWorktree, git worktree add, or git checkout -b.
   • NEVER commit or make changes to the main branch. If the current branch is main, STOP IMMEDIATELY and ask the user which branch to use.

2. Workflow:

   • Follow TDD as defined in AGENTS.md (>= 80% coverage).
   • Run cargo clippy && cargo fmt --check && cargo test to verify before committing.

3. No Pull Request Creation Without Explicit User Request:

   • NEVER create a pull request unless the user explicitly asks for one in the current task.
   • Do not run gh pr create as part of default completion.

Operation Protocol

1. Pre-Flight Safety Check (MANDATORY)

• Verify Branch: Run git branch --show-current. If on main, STOP and ask the user.
• Load Context: Read CLAUDE.md, docs/PRD.md, and docs/DESIGN.md.

2. Requirements

• Understand the task from the prompt, user request, or assignment file.
• Analyze the codebase to understand existing patterns and constraints.
• Ask clarifying questions if requirements are ambiguous.

3. Design

• Draft a design document with at least 2 options (more if appropriate).
• For each option, document:
  • Approach: How it would be implemented.
  • Pros: Benefits and strengths.
  • Cons: Drawbacks and risks.
  • Affected Files: List of files that would be modified/created.
• Include a recommendation with rationale.
• Save design to: docs/local/design-<feature-name>.md
• CRITICAL: NEVER overwrite existing files in docs/local/. Always use a unique filename.

4. Implementation Plan

• Create a comprehensive task list ordered by dependency.
• Include testing tasks alongside implementation tasks.
• Save the plan to: docs/local/plan-<feature-name>.md

5. Implementation (TDD)

• Follow the task list, marking items complete as you go.
• Red -> Green -> Refactor: write failing tests first, then implement.
• Unit tests go in #[cfg(test)] modules within the source file.
• Integration tests go in tests/ directory.
• Run cargo clippy && cargo fmt --check && cargo test to verify your changes.
• Ensure test coverage is >= 80% for new logic.

6. Documentation Updates

• If architectural decisions were made, add or update documents in docs/.
• Add future work items, out-of-scope tasks, or tech debt to docs/BACKLOG.md (create if needed).

7. Completion

• Commit the completed work when verification passes.
• Report the commit hash, verification results, and any remaining user-only steps.
• Only create a pull request if the user explicitly asks for one in the current task.