Add Droid CLI agent support

tools/cc-sdd/src/agents/registry.ts

@@ -196,6 +196,23 @@ export const agentDefinitions = {
     },
     manifestId: 'qwen-code',
   },
+  droid: {
+    label: 'Droid CLI',
+    description:
+      'Installs kiro prompts in `.factory/commands/`, droid subagents in `.factory/droids/`, shared settings in `{{KIRO_DIR}}/settings/`, and a DROID.md quickstart.',
+    aliasFlags: ['--droid', '--droid-cli'],
+    layout: {
+      commandsDir: '.factory/commands',
+      agentDir: '.factory/droids',
+      docFile: 'DROID.md',
+    },
+    commands: {
+      spec: '`/kiro:spec-quick <what-to-build>`',
+      steering: '`/kiro:steering`',
+      steeringCustom: '`/kiro:steering-custom <what-to-create-custom-steering-document>`',
+    },
+    manifestId: 'droid',
+  },
 } as const satisfies Record<string, AgentDefinition>;
 
 export type AgentType = keyof typeof agentDefinitions;

tools/cc-sdd/templates/agents/droid/commands/spec-design.md

@@ -0,0 +1,64 @@
+---
+description: Create comprehensive technical design for a specification
+allowed-tools: Read, Task
+argument-hint: <feature-name> [-y]
+---
+
+# Technical Design Generator
+
+## Parse Arguments
+- Feature name: `$1`
+- Auto-approve flag: `$2` (optional, "-y")
+
+## Validate
+Check that requirements have been completed:
+- Verify `{{KIRO_DIR}}/specs/$1/` exists
+- Verify `{{KIRO_DIR}}/specs/$1/requirements.md` exists
+
+If validation fails, inform user to complete requirements phase first.
+
+## Invoke Subagent
+
+Delegate design generation to spec-design-agent:
+
+Use the Task tool to invoke the Subagent with file path patterns:
+
+```
+Task(
+  subagent_type="spec-design-agent",
+  description="Generate technical design and update research log",
+  prompt="""
+Feature: $1
+Spec directory: {{KIRO_DIR}}/specs/$1/
+Auto-approve: {true if $2 == "-y", else false}
+
+File patterns to read:
+- {{KIRO_DIR}}/specs/$1/*.{json,md}
+- {{KIRO_DIR}}/steering/*.md
+- {{KIRO_DIR}}/settings/rules/design-*.md
+- {{KIRO_DIR}}/settings/templates/specs/design.md
+- {{KIRO_DIR}}/settings/templates/specs/research.md
+
+Discovery: auto-detect based on requirements
+Mode: {generate or merge based on design.md existence}
+Language: respect spec.json language for design.md/research.md outputs
+"""
+)
+```
+
+## Display Result
+
+Show Subagent summary to user, then provide next step guidance:
+
+### Next Phase: Task Generation
+
+**If Design Approved**:
+- Review generated design at `{{KIRO_DIR}}/specs/$1/design.md`
+- **Optional**: Run `/kiro:validate-design $1` for interactive quality review
+- Then `/kiro:spec-tasks $1 -y` to generate implementation tasks
+
+**If Modifications Needed**:
+- Provide feedback and re-run `/kiro:spec-design $1`
+- Existing design used as reference (merge mode)
+
+**Note**: Design approval is mandatory before proceeding to task generation.

tools/cc-sdd/templates/agents/droid/commands/spec-impl.md

@@ -0,0 +1,68 @@
+---
+description: Execute spec tasks using TDD methodology
+allowed-tools: Read, Task
+argument-hint: <feature-name> [task-numbers]
+---
+
+# Implementation Task Executor
+
+## Parse Arguments
+- Feature name: `$1`
+- Task numbers: `$2` (optional)
+  - Format: "1.1" (single task) or "1,2,3" (multiple tasks)
+  - If not provided: Execute all pending tasks
+
+## Validate
+Check that tasks have been generated:
+- Verify `{{KIRO_DIR}}/specs/$1/` exists
+- Verify `{{KIRO_DIR}}/specs/$1/tasks.md` exists
+
+If validation fails, inform user to complete tasks generation first.
+
+## Task Selection Logic
+
+**Parse task numbers from `$2`** (perform this in Slash Command before invoking Subagent):
+- If `$2` provided: Parse task numbers (e.g., "1.1", "1,2,3")
+- Otherwise: Read `{{KIRO_DIR}}/specs/$1/tasks.md` and find all unchecked tasks (`- [ ]`)
+
+## Invoke Subagent
+
+Delegate TDD implementation to spec-tdd-impl-agent:
+
+Use the Task tool to invoke the Subagent with file path patterns:
+
+```
+Task(
+  subagent_type="spec-tdd-impl-agent",
+  description="Execute TDD implementation",
+  prompt="""
+Feature: $1
+Spec directory: {{KIRO_DIR}}/specs/$1/
+Target tasks: {parsed task numbers or "all pending"}
+
+File patterns to read:
+- {{KIRO_DIR}}/specs/$1/*.{json,md}
+- {{KIRO_DIR}}/steering/*.md
+
+TDD Mode: strict (test-first)
+"""
+)
+```
+
+## Display Result
+
+Show Subagent summary to user, then provide next step guidance:
+
+### Task Execution
+
+**Execute specific task(s)**:
+- `/kiro:spec-impl $1 1.1` - Single task
+- `/kiro:spec-impl $1 1,2,3` - Multiple tasks
+
+**Execute all pending**:
+- `/kiro:spec-impl $1` - All unchecked tasks
+
+**Before Starting Implementation**:
+- **IMPORTANT**: Clear conversation history and free up context before running `/kiro:spec-impl`
+- This applies when starting first task OR switching between tasks
+- Fresh context ensures clean state and proper task focus

tools/cc-sdd/templates/agents/droid/commands/spec-init.md

@@ -0,0 +1,65 @@
+---
+description: Initialize a new specification with detailed project description
+allowed-tools: Bash, Read, Write, Glob
+argument-hint: <project-description>
+---
+
+# Spec Initialization
+
+<background_information>
+- **Mission**: Initialize the first phase of spec-driven development by creating directory structure and metadata for a new specification
+- **Success Criteria**:
+  - Generate appropriate feature name from project description
+  - Create unique spec structure without conflicts
+  - Provide clear path to next phase (requirements generation)
+</background_information>
+
+<instructions>
+## Core Task
+Generate a unique feature name from the project description ($ARGUMENTS) and initialize the specification structure.
+
+## Execution Steps
+1. **Check Uniqueness**: Verify `{{KIRO_DIR}}/specs/` for naming conflicts (append number suffix if needed)
+2. **Create Directory**: `{{KIRO_DIR}}/specs/[feature-name]/`
+3. **Initialize Files Using Templates**:
+   - Read `{{KIRO_DIR}}/settings/templates/specs/init.json`
+   - Read `{{KIRO_DIR}}/settings/templates/specs/requirements-init.md`
+   - Replace placeholders:
+     - `{{FEATURE_NAME}}` → generated feature name
+     - `{{TIMESTAMP}}` → current ISO 8601 timestamp
+     - `{{PROJECT_DESCRIPTION}}` → $ARGUMENTS
+   - Write `spec.json` and `requirements.md` to spec directory
+
+## Important Constraints
+- DO NOT generate requirements/design/tasks at this stage
+- Follow stage-by-stage development principles
+- Maintain strict phase separation
+- Only initialization is performed in this phase
+</instructions>
+
+## Tool Guidance
+- Use **Glob** to check existing spec directories for name uniqueness
+- Use **Read** to fetch templates: `init.json` and `requirements-init.md`
+- Use **Write** to create spec.json and requirements.md after placeholder replacement
+- Perform validation before any file write operation
+
+## Output Description
+Provide output in the language specified in `spec.json` with the following structure:
+
+1. **Generated Feature Name**: `feature-name` format with 1-2 sentence rationale
+2. **Project Summary**: Brief summary (1 sentence)
+3. **Created Files**: Bullet list with full paths
+4. **Next Step**: Command block showing `/kiro:spec-requirements <feature-name>`
+5. **Notes**: Explain why only initialization was performed (2-3 sentences on phase separation)
+
+**Format Requirements**:
+- Use Markdown headings (##, ###)
+- Wrap commands in code blocks
+- Keep total output concise (under 250 words)
+- Use clear, professional language per `spec.json.language`
+
+## Safety & Fallback
+- **Ambiguous Feature Name**: If feature name generation is unclear, propose 2-3 options and ask user to select
+- **Template Missing**: If template files don't exist in `{{KIRO_DIR}}/settings/templates/specs/`, report error with specific missing file path and suggest checking repository setup
+- **Directory Conflict**: If feature name already exists, append numeric suffix (e.g., `feature-name-2`) and notify user of automatic conflict resolution
+- **Write Failure**: Report error with specific path and suggest checking permissions or disk space