← all publishers

rabitarochan

@rabitarochan source repo

7 published skills

  1. Setup · rabitarochan
    Install SkDD into the current project. Deploys the skdd-harvest engine skill, backlog seed, optional Stop hook, the managed AGENTS.md section, and the CLAUDE.md import. Explicit invocation only (/skdd:setup).
    0 installs
  2. Config · rabitarochan
    Change SkDD's per-project settings — the harvest threshold (low/medium/high/max), the skill prefix, and whether the Stop hook is installed — then re-render the managed assets so every artifact agrees. Explicit invocation only (/skdd:config).
    0 installs
  3. Update · rabitarochan
    Update SkDD assets already deployed in the current project (skdd-harvest engine skill, Stop hook, managed AGENTS.md section) to the installed plugin version. Never touches the backlog or harvested skills. Explicit invocation only (/skdd:update).
    0 installs
  4. Skdd Harvest · rabitarochan bundle
    Structures and generates reusable Skills (SKILL.md) from knowledge discovered during conversations. The core skill of SkDD (Skill Driven Development). Use when: the user says "skillify", "harvest", "/harvest", "turn this into a skill", or "make a skill from this"; when the agent detects a skill candidate at task completion and the user approves; when updating an existing skill with new insights; when promoting a Proto-Skill to a full skill. Also consult for topics related to SkDD, knowledge management, or tacit-to-explicit knowledge conversion.
    0 installs
  5. Design Adr · rabitarochan
    Work through a single architectural decision in dialogue and record it as an Architecture Decision Record (ADR) in Nygard format, capturing the context, the decision, and the consequences that come with it. Use this when the user is weighing one specific technical decision, or wants to record one they have already made. Trigger on phrases like "ADR", "architecture decision record", "record this decision", "should we use X or Y", "どちらを採用すべきか", "技術選定", "この決定を記録したい", "アーキテクチャ決定記録", "AとBで迷っている". Use this even when the user has not said the word "ADR" — if they are weighing one decision whose reasoning will matter later, this skill applies. For designing a whole project or a whole feature, use design-new-project or design-feature instead.
    0 installs
  6. Design Feature · rabitarochan
    Design a new feature or a change to an existing system through structured dialogue, after investigating how the existing codebase actually works, then write a design document that records the decisions and how they fit the system's existing design. Use this whenever the user wants to add to, extend, or modify something that already exists and wants the design thought through before implementation. Trigger on phrases like "add a feature", "design this change", "extend the system", "機能追加の設計", "この機能を設計したい", "既存システムに追加", "改修の設計", "設計ドキュメントを書きたい". Use this even when the user has not said "design document" — if they are about to change a system with existing design decisions and the approach is not yet settled, this skill applies. For something built from scratch with no existing design to respect, use design-new-project instead.
    0 installs
  7. Design New Project · rabitarochan
    Design a new project or system from scratch through structured dialogue, then write a design document that captures the decisions and the reasoning behind them. Use this whenever the user is starting something new — a new system, service, application, library, or a rewrite — and wants to think the design through before writing code. Trigger on phrases like "new project", "design a system", "starting from scratch", "design doc", "設計ドキュメント", "新規プロジェクトの設計", "これから作るシステムの設計", "ゼロから設計したい", "設計を詰めたい". Use this even when the user has not said the words "design document" — if they are about to build something new and the requirements or architecture are not yet settled, this skill applies. For adding a feature to something that already exists, use design-feature instead.
    0 installs