Brummel/Skills
1
0
Fork 0
Code Issues 3 Pull Requests Actions Packages Projects Releases Wiki Activity

migration.md layout tree and README migration-status are stale #5

New Issue
Closed
opened 2026-06-04 23:24:24 +02:00 by Brummel · 0 comments
Brummel commented 2026-06-04 23:24:24 +02:00
Owner
Copy Link
Copy Source

The architect flagged this during the specify-entry-path cycle close as pre-existing debt (not introduced by that cycle).

Two stale renderings of the skill roster:

  • docs/migration.md 'Expected layout after migration' tree (around line 17) omits the skill directories added since it was written: tdd/, glossary/, pseudo/, issue/, postmortem/. The tree predates all of them (the cycle did add specify/ to it).
  • README.md Status section (around line 142) still says migration 'is in progress' and 'the remaining seven skills follow' — but the roster has long since landed.

Decide per item whether to bring each current or retire it (migration.md may have served its purpose as a one-time migration tracker). Out of scope for the specify cycle; filed so the drift is not silently carried.

context: surfaced by audit architect review at the specify-entry-path cycle close

The architect flagged this during the specify-entry-path cycle close as pre-existing debt (not introduced by that cycle). Two stale renderings of the skill roster: - docs/migration.md 'Expected layout after migration' tree (around line 17) omits the skill directories added since it was written: tdd/, glossary/, pseudo/, issue/, postmortem/. The tree predates all of them (the cycle did add specify/ to it). - README.md Status section (around line 142) still says migration 'is in progress' and 'the remaining seven skills follow' — but the roster has long since landed. Decide per item whether to bring each current or retire it (migration.md may have served its purpose as a one-time migration tracker). Out of scope for the specify cycle; filed so the drift is not silently carried. context: surfaced by audit architect review at the specify-entry-path cycle close
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
BLOCKER
Kernfunktionalität kaputt; preemptet jede andere Auswahl
 bug
beobachtbares Fehlverhalten
 feature
substantielle Erweiterung, kein voller Spec nötig
 idea
kann gestrichen werden, kein Commitment
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claude (Claude) Brummel
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Brummel/Skills#5
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?