chore: update skills

Author: tomkis

.agents/skills/plan/SKILL.md .agents/skills/spec/SKILL.md.agents/skills/plan/SKILL.md renamed to .agents/skills/spec/SKILL.md

@@ -1,22 +1,22 @@
 ---
-name: plan
+name: spec
 description: >
-  Plan a feature or change with full knowledge of the opinionated TypeScript architecture and the project's adoption state.
+  Spec out a feature or change with full knowledge of the opinionated TypeScript architecture and the project's adoption state.
   Conducts a thorough discovery interview to understand domain concerns, bounded contexts, and application services,
   then produces a high-level architectural specification — never concrete implementation details.
-  Triggers on phrases like "plan a feature", "design this change", "architect this",
-  "help me plan", "what modules do I need", or "think through this feature".
-  Also invocable via the /tseng:plan slash command.
+  Triggers on phrases like "spec this feature", "design this change", "architect this",
+  "help me spec", "what modules do I need", or "think through this feature".
+  Also invocable via the /tseng:spec slash command.
 ---
 
 ```!
 echo "Architecture docs: ${CLAUDE_SKILL_DIR}/architecture/"
 echo "Version: $(cat "${CLAUDE_SKILL_DIR}/VERSION")"
 ```
 
-# TSEng Plan
+# TSEng Spec
 
-Plans features and changes with full knowledge of the opinionated TypeScript architecture and the project's current adoption state. Produces a high-level architectural specification through rigorous discovery — never concrete implementation details.
+Specs out features and changes with full knowledge of the opinionated TypeScript architecture and the project's current adoption state. Produces a high-level architectural specification through rigorous discovery — never concrete implementation details.
 
 The output is a specification that gives the implementer architectural guardrails (which modules, which layers, which events, which services etc.) while leaving room for creative decisions about *how* to implement each piece.
 
@@ -233,7 +233,7 @@ If yes:
 3. Create the issue using `gh issue create`.
 4. Report the issue URL to the user.
 
-The issue body should be the specification from Phase 5, formatted for GitHub readability. Include a header noting it was generated by TSEng Plan with the architecture version.
+The issue body should be the specification from Phase 5, formatted for GitHub readability. Include a header noting it was generated by TSEng Spec with the architecture version.
 
 ## Guidelines
 

.agents/skills/plan/VERSION .agents/skills/spec/VERSION.agents/skills/plan/VERSION renamed to .agents/skills/spec/VERSION

@@ -0,0 +1 @@
+../../.agents/skills/spec