FACTUAL ACTIVITY RECORD · An activity record based on work that took place
Unifying basic Issue, branch, and PR operations
Combining actor-specific write authority and a fixed Issue template in one rule set
Purpose
Work-unit creation, handling of added requests, repository write authority, and Issue formatting were spread across multiple assumptions.
Implementation
AGENTS.md documented the then-current one-to-one mapping of a work unit to one Issue, branch, and PR; the default of expanding the active Issue for added requests; and the boundary that only Mako changes repository state. Issue bodies were standardized to a fixed order and template covering Story, background, INVEST, completion conditions, and dependencies.
- リポジトリまたはGitHub上の状態を変更する操作は、メインエージェントだけが実施してください。これには、Issueの作成、作業ブランチの作成・切り替え、fetch、pull、merge、rebaseなどのbranch/ref更新、ステージング、コミット、push、およびIssueやPRの作成・更新・コメント・レビュー投稿・マージを含み、サブエージェントには実施させないでください。
- サブエージェントは、調査、検証、独立レビューに必要なread-onlyのgit操作およびGitHub操作を実施できます。ただし、前項の状態変更操作は実施してはなりません。
- 1つのIssueには、1つの作業ブランチと1つのPRを対応させてください。Rendering diagram…
What was confirmed
Verification results
The documented rules and template were checked for required sections, all six INVEST items, unchecked completion boxes, and dependency notation.
Migration of every existing Issue to the new format was outside this cutoff.
Basis for completion
The work was complete when work units, write authority, and Issue-writing standards could be read as one operating rule set.