arinyaho/concord

Show or update Concord's persistent north-star framing for the current project, especially when context must survive a new GitHub Copilot session.

Use when a product brief, problem report, strategic objective, or set of incomplete tickets must be investigated, turned into one or more implementation-ready tickets, and driven through verified PRs. Do NOT use when one ticket is already implementation-ready; use ticket-to-pr instead. Do NOT use for ticket drafting without implementation; use ticket-writing instead.

Create or substantially revise editable bid and proposal slide decks, including implementing review feedback, from RFPs, source evidence, and reference decks. Use when evaluator alignment, requirement traceability, presentation narrative, native editability, and export-safe visual quality matter. Do not use for review-only requests or isolated typo fixes.

Run Concord's deterministic review-and-fix loop with independently selected Claude, Codex, or Copilot reviewer and fixer providers and models.

Use when an open GitHub PR must be monitored until the GitHub Codex bot gives an explicit LGTM reaction, rather than merely completing its review.

Use when a request names a unit of work and asks for it to be taken through several stages at once — "이 티켓 설계부터 PR까지", "take this issue through design, implementation and a PR", "이거 끝까지 해서 PR 올려줘". Do NOT use for a single-stage request (just fix this, just review this).

Use when a user asks to draft, create, file, rewrite, refine, or update a development ticket or issue in Notion, Jira, GitHub Issues, or another tracker, especially when another agent will implement from it.