Repository navigation
[Task] Inventory and classify .github prompt assets with final target mapping #737
Description
Parent issue: #736
Template source: .github/ISSUE_TEMPLATE/22-audit.md\nTemplate label: 🛡️ Audit\nSpec source: .github/projects/active/refactor-migrate-prompts/openspec-strict/children/01-1-task-inventory-and-classify-prompts.md\n\n---\n## Template Base\n\n
Audit Summary
Audit Checklist / Scope
- Scope defined and agreed
- Areas/components listed
- Audit tools or standards referenced
- Risks and findings documented
- Remediation actions mapped
Findings / Risks
Remediation Actions
Acceptance Criteria
- Audit scope and checklist completed
- Findings and risks documented
- Remediation actions assigned and tracked
- Documentation/changelog updated (if applicable)
- PR uses correct branch prefix (audit/)
Additional Context
Definition of Ready (DoR)
- Audit scope, checklist, and goals defined
- Areas/components listed
- Dependencies and standards mapped
Definition of Done (DoD)
- Audit performed and findings documented
- Remediation actions assigned
- Documentation/changelog updated (if applicable)
- PR uses correct branch prefix (audit/)
---\n\n---\n## Spec Details\n\n## template-map
- template_file:
.github/ISSUE_TEMPLATE/22-audit.md
Deliverables
- Final migration matrix covering all source prompts.
- Explicit rename/target mapping for every moved prompt.
- Successor mapping for every merged/deprecated prompt.
Acceptance Criteria
- Matrix coverage equals source prompt count.
- Every
movehas a concreteprompts/*.prompttarget path. - Every
merge/deprecatehas a named successor prompt. - Action counts are internally consistent with matrix rows.
Activity
linear-code commentedon Jun 1, 2026
LS-877
LS-1116
ashleyshaw commentedon Jun 1, 2026
Completed.
Acceptance criteria evidence:
References:
ashleyshaw commentedon Jun 1, 2026
Closing as complete. Evidence and artefacts linked in the latest comment.
ashleyshaw commentedon Jun 1, 2026
Implemented in PR #748: #748 (merged).
github-actions commentedon Sep 8, 2026
This issue has labels that are not in the canonical taxonomy:
migrate:priority:importantmigrate:status:donemigrate:type:auditmigrate:area:documentationValid Canonical Labels
Please use labels with a prefix from the canonical taxonomy:
type:bug,type:feature,type:task,type:documentation, etc.status:needs-triage,status:in-progress,status:done, etc.priority:critical,priority:high,priority:normal,priority:lowarea:ci,area:docs,area:labels,area:security, etc.meta:needs-changelog,meta:duplicate,meta:blocked, etc.For the complete list, see .github/labels.yml.
eleshar commentedon Oct 1, 2026
status:donedoes not hold — the migration happened, the classification did notRe-verified against
developate30867e4cf. This issue asks for a prompt inventory and classification with a final target mapping. What exists is a migration execution record, which is a different artefact.What is on
develop:.github/reports/prompt-migration-2026-09-04.md— 71 prompts moved from.github/prompts/toprompts/, statuscompleted, filed 2026-09-04. It records the move and preserves git history. It contains two occurrences of "classif"/"inventory" and no classification table.prompts/holds 104 files;.github/prompts/is down toREADME.mdandprompts.md.What is missing:
developis.github/projects/archived/portable-ai-plugin-restructure/portable-ai-plugin-restructure-legacy-prompts-classification-report-2026-05-26.md, which is from the portable-AI programme, not this one..github/projects/active/refactor-migrate-prompts/openspec-strict/children/01-1-task-inventory-and-classify-prompts.md, is absent fromdevelop. So the acceptance criteria cannot be checked against the spec that defined them.Why the label was removed. A migration record is not the deliverable this task names, and the spec that would define "done" no longer exists on
develop.status:donewas asserting a completion nobody can verify. It has been removed and the issue returned tostatus:needs-triage.What would make this genuinely done: either recover the classification from the archived programme and state the target mapping, or re-scope the issue to "migration executed" and close it on that basis. Those are different decisions, so neither has been taken here.
Related: #736 is the parent epic. #739 and #740 are the sibling tasks.