fix: Consolidate-Tasks preserves dates and chronological order#175
Open
MarkMichaelis wants to merge 1 commit into
Open
fix: Consolidate-Tasks preserves dates and chronological order#175MarkMichaelis wants to merge 1 commit into
MarkMichaelis wants to merge 1 commit into
Conversation
Get-FeatureSlug stripped the leading YYYY-MM-DD- prefix from every imported artifact, discarding the only ordering signal legacy design notes and PRDs carried. The date was recorded nowhere. - Preserve an embedded YYYY-MM-DD- prefix on the destination name. - Add -InsertDatePrefix (default on): for sources lacking an embedded date, synthesize a prefix from the most recent git commit date, falling back to the file's last-write time. - Add a Source Date column to tasks/MIGRATION.md; sort rows chronologically. - New helpers Get-DatePrefix, Get-GitDate, Get-SourceDate; tests for each plus integration coverage; update help and tasks/README.md. New agent-created PRDs/plans intentionally keep the bare <feature> slug so the @prd/@plan agents can resolve them by exact path. Closes #174 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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
Consolidate-Tasks.ps1stripped the leadingYYYY-MM-DD-prefix from everyimported artifact via
Get-FeatureSlug, discarding the only chronologicalordering signal that legacy design notes / PRDs carried. The date was recorded
nowhere -- a real run collapsed seven dated design notes into undated slugs.
Changes
YYYY-MM-DD-prefix on the destination name so thetasks/listing sorts chronologically.-InsertDatePrefixswitch(default on): most-recent git commit date, falling back to the file's
last-write time. Pass
-InsertDatePrefix:$falseto opt out.tasks/MIGRATION.mdand sort rowschronologically.
Get-DatePrefix,Get-GitDate,Get-SourceDatewith unittasks/README.md.Scope decision (needs sign-off)
New
@prd/@planartifacts intentionally keep the bare<feature>slug(no date, no issue number in the filename) so the agents can resolve them by
exact path. Their ordering/identity lives in the branch (
feat/<issue#>-...),issue, and git history -- not the filename. Date-prefixing new files would
require switching the agents to glob lookups, a cross-cutting change to the
upstream naming convention affecting all consumers. Deliberately not done
here. See the open question below.
Open question
Should newly created PRDs/plans also carry a sortable prefix (date or issue
number) in the filename, accepting the agent-lookup change? Flagging for a human
decision rather than guessing.
Test
Closes #174