Team developer

You build stories with an agent in a team, and review what it opens.

You build stories with a coding agent inside a team. Your agent needs to know what binds for the story in front of it — the requirement, its criteria, the constraints and decisions around it — and your teammates need to trust that what it builds matches what was agreed.

In CorPole your agent connects under your own name and acts with your permissions. It reads the story's work context before it touches code, names the codes it follows in the branch and the pull request, registers tests against the criteria, and leaves a handover note when it stops halfway. You write your own agent rules on top of the solution's.

This page gathers what a developer needs: connecting, setting up the repository, picking up Ready work in an initiative, the change-request check on pull and merge requests, and what to do when the agent goes off course.

Start here

  1. Connect your agent under your own identity: OAuth, or a personal agent token.
  2. Run /corpole:init in the repository so the agent puts CorPole above the files in the repo.
  3. Ask the agent to pick a Ready story; it reads the story's work context before coding.
  4. Name the story or record code in the branch and pull request, so the check and the traceability line up.
  5. Write your own rules for the agent, on top of the solution's.

Getting started

Connect your agent

Records & authority

Relations & conflicts

Work & boards

Knowledge

Agent policy & rules

Traceability & quality

Existing codebases

When things go wrong

Team & accounts

Security & data

Troubleshooting

Reference

Feedback for CorPole