docs: propose ExecPlans for complex changes - #174
Open
Tsuyoshi Ushio (TsuyoshiUshio) wants to merge 4 commits into
Open
docs: propose ExecPlans for complex changes#174Tsuyoshi Ushio (TsuyoshiUshio) wants to merge 4 commits into
Tsuyoshi Ushio (TsuyoshiUshio) wants to merge 4 commits into
Conversation
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
This reverts commit 0efa240. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 3b5a7e42-f11f-4f3f-b488-18abaee5fc76
This was referenced Aug 24, 2026
Tsuyoshi Ushio (TsuyoshiUshio)
marked this pull request as ready for review
August 26, 2026 03:11
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This draft proposes ExecPlans as a possible lightweight planning aid for complex changes. It is a request for feedback on whether and how this repository should adopt ExecPlans, not a finalized policy. No ExecPlan is created or executed by this PR, and the existing FRD workflow remains unchanged while the proposal is discussed.
The approach in
PLANS.mdis adapted from openai/openai-agents-js.Proposed changes
PLANS.mdwith a self-contained ExecPlan format, authoring guidance, required living-document sections, and a reusable template.AGENTS.mdsection suggesting ExecPlans for complex features or significant refactors and locating them underplans/.plans/to.gitignore, representing the proposal that working plans remain local by default.Example for discussion
PR #170 produced a concrete ExecPlan that reviewers can inspect at this immutable permalink: dynamic workflow task execution policy ExecPlan.
That document is linked only as a reviewable example produced during PR #170. It is not added to this PR, reviewers do not need to check out another branch to read it, and this proposal does not require adopting its specific contents.
Feedback requested
Please share feedback on:
plans/remain local and ignored, or should some/all plans be committed for durable review and history?PLANS.mdtemplate appropriately prescriptive, or should it be simplified or made more flexible?