tech-debt: relocate skills-guide.md into guidelines (follow-up to #365)

[rucka]

Story Statement

As a maintainer of the Pair KB
I want skills-guide.md relocated from the .pair/knowledge/ root into its correct guidelines location (same class of move as #365)
So that this loose top-level file stops reading as "guidelines dumped at the root" — catalogued, discoverable, registered like the rest of guidelines/

Epic Context

Parent Epic: None — standalone tech-debt / KB-structure hygiene, same lineage as #365.
Status: Todo
Priority: P2 (Could-Have)

Status Workflow

• Todo: Story is created but not yet refined
• Refined: Story is detailed, estimated, and ready for development
• In Progress: Story is actively being developed
• Done: Story delivered and accepted

User Value

User Benefit: Consistent, discoverable KB structure — no top-level file that isn't catalogued.
Business Impact: KB structural hygiene; low risk, low urgency.
Visible UI Value: N/A (KB/docs structure only).

Rough Sizing

Story Points: XS(1)
Confidence: Medium
Reasoning: Same mechanical shape as #365 (relocate + rewrite refs + register + regenerate mirror) but a single file, not a 9-file cohesive folder — smaller blast radius.

Initial Scope

Likely In Scope

• git mv of dataset/.pair/knowledge/skills-guide.md into its correct guidelines subfolder (destination TBD at refinement — likely guidelines/technical-standards/ai-development/, alongside skill-conventions/).
• Rewrite every reference to the old path (dataset SKILL.md pointers + any prose/test refs — grep first, don't assume link-only like tech-debt: relocate skill-conventions/ into guidelines (technical-standards/ai-development) #365 found).
• Register in the relevant guidelines catalog(s).
• Regenerate the root mirror via pair update; check:links green on dataset + root.

Likely Out of Scope

• Any content change to skills-guide.md itself (pure relocation, per tech-debt: relocate skill-conventions/ into guidelines (technical-standards/ai-development) #365 precedent).
• Folding skills-guide.md into skill-conventions/ (separate design call, not assumed here — decide destination at refinement).

Open Questions

• Exact destination folder for skills-guide.md (KB-structure decision, not assumed by this filing).
• Whether it should be merged into skill-conventions/README.md instead of relocated standalone.

Definition of Done Expectations

Standard DoD Requirements (to be detailed during refinement):

• File relocated, all references rewritten
• Registered in the applicable guidelines catalog(s)
• check:links green (dataset + root); root mirror byte-consistent
• No content change inside the moved file
• Code reviewed and merged

Dependencies

Story Dependencies: Precedent — #365 (skill-conventions relocation), explicitly flagged this file as an out-of-scope follow-up.
Epic Dependencies: None.

Notes

Filed per #365's Edge-Cases note ("skills-guide.md sibling smell — also a loose top-level file — explicitly out of scope, flag as a follow-up story"). Not refined yet — destination folder and exact ref-rewrite scope to be nailed down at refinement.