Convert Terraphim skills to Clawdbot skills (v0)

[AlexMikhalev]

Goal

Convert Terraphim Claude Code plugin skills in this repo into Clawdbot skills (Clawdbot format) so they can be used by Clawdbot agents.

Scope (initial)

• Convert the text/prompt-based skills first (e.g. disciplined-research, disciplined-design, disciplined-implementation, disciplined-specification, disciplined-verification, disciplined-validation, etc.).
• Defer hook/agent binary features (terraphim-agent, .claude-plugin, Claude-specific hook wiring) to a later phase.

Inventory

Source directories to port:

• skills/*/SKILL.md (primary)
• any skills/*/reference/** and skills/*/examples/**

Non-goals in v0:

• Installing / running terraphim-agent
• Claude Code hook replacement

Deliverables

1. A new Clawdbot-compatible skill package directory, e.g.
   • clawdbot-skills/terraphim-engineering/ (name TBD)
   • or individual Clawdbot skills per Terraphim skill.
2. Each converted skill includes:
   • SKILL.md (Clawdbot-facing instructions / trigger phrases)
   • any supporting docs/assets
   • clear mapping from Terraphim skill name → Clawdbot skill name
3. A short MIGRATION.md explaining:
   • what was ported
   • what was not
   • how to use in Clawdbot

Proposed approach (very specific)

Phase 0 — Decide target packaging

• Decide if we want one Clawdbot skill per Terraphim skill (recommended for modularity) vs a single “bundle skill”.
• Decide final names/triggers.

Phase 1 — Build conversion rules

Create a deterministic conversion rubric:

• For each skills/<name>/SKILL.md, extract:
  • name, description, triggers, usage sections, “system prompt” blocks.
• Rewrite Claude-specific bits:
  • Replace claude plugin … references with Clawdbot usage.
  • Remove/flag .claude-plugin and ~/.claude/settings.local.json instructions.
• Preserve all prompt content verbatim where possible.

Phase 2 — Create Clawdbot skill skeleton(s)

For each Terraphim skill folder:

• Create clawdbot-skills/<skill-name>/SKILL.md
• Add any extra docs as local files.
• Add triggers matching common user phrasing:
  • e.g. disciplined research, disciplined design, etc.

Phase 3 — Add runtime tooling (optional, only if needed)

If any Terraphim skills require automation beyond prompting:

• Implement a thin Node wrapper in the Clawdbot skill (scripts) for:
  • reading local files
  • templating prompts
  • producing structured outputs

Phase 4 — Validation

• Smoke-test each converted skill by prompting Clawdbot to use it.
• Ensure no Claude-only paths remain.

Acceptance criteria

• At least these skills are usable from Clawdbot end-to-end:
  • disciplined-research
  • disciplined-design
  • disciplined-implementation
  • disciplined-specification
  • disciplined-verification
  • disciplined-validation
• Clear docs for installation/usage in Clawdbot.

Notes / references

This repo structure:

• skills live under skills/*/SKILL.md
• Claude plugin instructions live in README.md