team-prlisted

# Team PR — Create the Pull Request Run the PR phase. Two modes: - **Resume mode** — Implement passed the aggregate gate. The topic branch has slice commits ready. `$ARGUMENTS/task.md` and `$ARGUMENTS/design.md` exist. - **Standalone mode** — no matching artifact directory, but the working tree has commits or staged changes ready to ship. Treat the current branch as the work source. ## Input `$ARGUMENTS` is the artifact directory: `docs/plans/<id>/`. If empty, the discovery block below resolves it for the **resume** path (discovery only augments resume — the standalone path is unchanged). The PR description is grounded in `$ARGUMENTS/design.md`. The ticket identifier (if any) is read from `$ARGUMENTS/task.md`'s frontmatter. Resolve the artifact directory by running this self-contained block (one bash call — agent threads reset cwd between calls): ```sh # Three-tier artifact-directory discovery (archetype A). # ID_RE + PHASE_FILES canonical from hooks/session-start-recover.mjs. # PHASE_FILES recency mirrors findActiveTopic() in session-start-recover.mjs. # NOTE: this block is duplicated across 8 skills by design (see docs/architecture.md); future: shared discover-topic.sh. ID_RE='^([A-Za-z][A-Za-z0-9_]*-[0-9]+|[0-9]{4}-[0-9]{2}-[0-9]{2})-[a-z0-9][a-z0-9-]*$' PHASE_FILES="task questions research design structure plan" # design.md is a lenient discovery proxy: the canonical PR-phase predecessor is # "aggregate gate passed" (no single artifact), so we key on design