Name: requirements
Author: yamat47

Prompt file imported from yamat47/project-boilerplate (.claude/commands/kiro/requirements.md). Fill in {{arguments}} before use. Copyright stays with the author.

Context

Task description: {{arguments}}
Existing codebase: OneCareer Report Rails application

Your task

1. Create directory

Create docs/specs directory if it doesn't exist

2. Understand existing implementation

Before analyzing new requirements:

Search and read relevant existing code
Understand current functionality
Identify integration points
Check for similar patterns in codebase

3. Analyze the task

Based on task type, extract:

For Bug Fixes:

Bug symptoms and reproduction steps
Root cause analysis approach
Expected correct behavior
Affected components

For Enhancements:

Current functionality gaps
Desired improvements
User impact
Technical constraints

4. Create Requirements Document

Create docs/specs/requirements.md with structure adapted to task type:

For Bug Fixes:

# Bug Fix Requirements - [Bug Summary]

## 1. Issue Overview
- Environment: [Production/Development]
- Affected scope: [Affected users/features]
- Priority: [Urgent/High/Medium/Low]

## 2. Symptoms
### 2.1 Reproduction Steps
1. [Step 1]
2. [Step 2]

### 2.2 Expected Behavior
- [Description of correct behavior]

### 2.3 Actual Behavior
- [Description of bug behavior]

## 3. Root Cause Analysis
- Suspected cause: [Cause inferred from code analysis]
- Related files: [file_path:line_number]

## 4. Fix Approach
- [ ] [Fix approach 1]
- [ ] [Fix approach 2 if needed]

## 5. Test Plan
- [ ] Bug reproduction test
- [ ] Post-fix verification
- [ ] Regression test scope

For Enhancements:

# Enhancement Requirements - [Feature Name]

## 1. Background and Purpose
- Current challenges: [Issues with existing functionality]
- Improvement goals: [What we want to achieve]

## 2. Enhancement Details
### 2.1 Scope of Changes
- Target features: [Features to be modified]
- Related files: 
  - [file_path:line_number - role]
  - [file_path:line_number - role]

### 2.2 Functional Changes
- [ ] [Change 1: Specific change details]
- [ ] [Change 2: Specific change details]

### 2.3 UI/UX Changes (if applicable)
- [ ] [Screen/interaction changes]

## 3. Technical Requirements
### 3.1 Technologies Used
- Existing: [Currently used technologies]
- New: [Technologies to be introduced]

### 3.2 Compatibility
- [ ] Maintain compatibility with existing data
- [ ] API backward compatibility

## 4. Success Criteria
- [ ] [Measurable completion criterion 1]
- [ ] [Measurable completion criterion 2]

## 5. Risks and Mitigations
- Risk: [Identified risks]
- Mitigation: [Risk mitigation strategies]

5. Add implementation notes

Include section for:

Existing code patterns to follow
Similar implementations in codebase
Potential impacts on other features

6. Create TODO entry

Use TodoWrite to add task based on type:

Bug fix: "Bug fix requirements analysis complete"
Enhancement: "Enhancement requirements definition complete"

7. Present to user

Show the requirements and:

Highlight critical findings from code analysis
Confirm understanding of the issue/enhancement
Get approval for proposed approach

Important Notes

Focus on existing code understanding
Keep documentation proportional to task size
Include specific file/line references
Consider impact on existing tests
Document any technical debt encountered

think hard

Install requirements and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

## Context - Task description: {{arguments}} - Existing codebase: OneCareer Report Rails application ## Your task ### 1. Create directory - Create `docs/specs` directory if it doesn't exist ### 2. Understand existing implementation Before analyzing new requirements: - Search and read relevant existing code - Understand current functionality - Identify integration points - Check for similar patterns in codebase ### 3. Analyze the task Based on task type, extract: **For Bug Fixes:** - Bug symptoms and reproduction steps - Root cause analysis approach - Expected correct behavior - Affected components **For Enhancements:** - Current functionality gaps - Desired improvements - User impact - Technical constraints ### 4. Create Requirements Document Create `docs/specs/requirements.md` with structure adapted to task type: **For Bug Fixes:** ```markdown # Bug Fix Requirements - [Bug Summary] ## 1. Issue Overview - Environment: [Production/Development] - Affected scope: [Affected users/features] - Priority: [Urgent/High/Medium/Low] ## 2. Symptoms ### 2.1 Reproduction Steps 1. [Step 1] 2. [Step 2] ### 2.2 Expected Behavior - [Description of correct behavior] ### 2.3 Actual Behavior - [Description of bug behavior] ## 3. Root Cause Analysis - Suspected cause: [Cause inferred from code analysis] - Related files: [file_path:line_number] ## 4. Fix Approach - [ ] [Fix approach 1] - [ ] [Fix approach 2 if needed] ## 5. Test Plan - [ ] Bug reproduction test - [ ] Post-fix verification - [ ] Regression test scope ``` **For Enhancements:** ```markdown # Enhancement Requirements - [Feature Name] ## 1. Background and Purpose - Current challenges: [Issues with existing functionality] - Improvement goals: [What we want to achieve] ## 2. Enhancement Details ### 2.1 Scope of Changes - Target features: [Features to be modified] - Related files: - [file_path:line_number - role] - [file_path:line_number - role] ### 2.2 Functional Changes - [ ] [Change 1: Specific change details] - [ ] [Change 2: Specific change details] ### 2.3 UI/UX Changes (if applicable) - [ ] [Screen/interaction changes] ## 3. Technical Requirements ### 3.1 Technologies Used - Existing: [Currently used technologies] - New: [Technologies to be introduced] ### 3.2 Compatibility - [ ] Maintain compatibility with existing data - [ ] API backward compatibility ## 4. Success Criteria - [ ] [Measurable completion criterion 1] - [ ] [Measurable completion criterion 2] ## 5. Risks and Mitigations - Risk: [Identified risks] - Mitigation: [Risk mitigation strategies] ``` ### 5. Add implementation notes Include section for: - Existing code patterns to follow - Similar implementations in codebase - Potential impacts on other features ### 6. Create TODO entry Use TodoWrite to add task based on type: - Bug fix: "Bug fix requirements analysis complete" - Enhancement: "Enhancement requirements definition complete" ### 7. Present to user Show the requirements and: - Highlight critical findings from code analysis - Confirm understanding of the issue/enhancement - Get approval for proposed approach ## Important Notes - Focus on existing code understanding - Keep documentation proportional to task size - Include specific file/line references - Consider impact on existing tests - Document any technical debt encountered think hard

{ "prompt": "## Context\n\n- Task description: {{arguments}}\n- Existing codebase: OneCareer Report Rails application\n\n## Your task\n\n### 1. Create directory\n\n- Create `docs/specs` directory if it doesn't exist\n\n### 2. Understand existing implementation\n\nBefore analyzing new requirements:\n- Search and read relevant existing code\n- Understand current functionality\n- Identify integration points\n- Check for similar patterns in codebase\n\n### 3. Analyze the task\n\nBased on task type, extract:\n\n**For Bug Fixes:**\n- Bug symptoms and reproduction steps\n- Root cause analysis approach\n- Expected correct behavior\n- Affected components\n\n**For Enhancements:**\n- Current functionality gaps\n- Desired improvements\n- User impact\n- Technical constraints\n\n### 4. Create Requirements Document\n\nCreate `docs/specs/requirements.md` with structure adapted to task type:\n\n**For Bug Fixes:**\n```markdown\n# Bug Fix Requirements - [Bug Summary]\n\n## 1. Issue Overview\n- Environment: [Production/Development]\n- Affected scope: [Affected users/features]\n- Priority: [Urgent/High/Medium/Low]\n\n## 2. Symptoms\n### 2.1 Reproduction Steps\n1. [Step 1]\n2. [Step 2]\n\n### 2.2 Expected Behavior\n- [Description of correct behavior]\n\n### 2.3 Actual Behavior\n- [Description of bug behavior]\n\n## 3. Root Cause Analysis\n- Suspected cause: [Cause inferred from code analysis]\n- Related files: [file_path:line_number]\n\n## 4. Fix Approach\n- [ ] [Fix approach 1]\n- [ ] [Fix approach 2 if needed]\n\n## 5. Test Plan\n- [ ] Bug reproduction test\n- [ ] Post-fix verification\n- [ ] Regression test scope\n```\n\n**For Enhancements:**\n```markdown\n# Enhancement Requirements - [Feature Name]\n\n## 1. Background and Purpose\n- Current challenges: [Issues with existing functionality]\n- Improvement goals: [What we want to achieve]\n\n## 2. Enhancement Details\n### 2.1 Scope of Changes\n- Target features: [Features to be modified]\n- Related files: \n - [file_path:line_number - role]\n - [file_path:line_number - role]\n\n### 2.2 Functional Changes\n- [ ] [Change 1: Specific change details]\n- [ ] [Change 2: Specific change details]\n\n### 2.3 UI/UX Changes (if applicable)\n- [ ] [Screen/interaction changes]\n\n## 3. Technical Requirements\n### 3.1 Technologies Used\n- Existing: [Currently used technologies]\n- New: [Technologies to be introduced]\n\n### 3.2 Compatibility\n- [ ] Maintain compatibility with existing data\n- [ ] API backward compatibility\n\n## 4. Success Criteria\n- [ ] [Measurable completion criterion 1]\n- [ ] [Measurable completion criterion 2]\n\n## 5. Risks and Mitigations\n- Risk: [Identified risks]\n- Mitigation: [Risk mitigation strategies]\n```\n\n### 5. Add implementation notes\n\nInclude section for:\n- Existing code patterns to follow\n- Similar implementations in codebase\n- Potential impacts on other features\n\n### 6. Create TODO entry\n\nUse TodoWrite to add task based on type:\n- Bug fix: \"Bug fix requirements analysis complete\"\n- Enhancement: \"Enhancement requirements definition complete\"\n\n### 7. Present to user\n\nShow the requirements and:\n- Highlight critical findings from code analysis\n- Confirm understanding of the issue/enhancement\n- Get approval for proposed approach\n\n## Important Notes\n\n- Focus on existing code understanding\n- Keep documentation proportional to task size\n- Include specific file/line references\n- Consider impact on existing tests\n- Document any technical debt encountered\n\nthink hard", "variables": [ "arguments" ], "notes": "Analyze requirements for enhancement or bug fix (Stage 1 of Spec-Driven Development) Tools: TodoWrite, TodoRead, Read, Write, MultiEdit, Bash(mkdir:*), Grep, Glob, Task.", "metadata": { "source": { "provider": "github-claude-commands", "repository": "https://github.com/yamat47/project-boilerplate", "path": ".claude/commands/kiro/requirements.md", "ref": "bcd1864ef2f23d85e6b978b0576448445f2276f3", "url": "https://github.com/yamat47/project-boilerplate/blob/bcd1864ef2f23d85e6b978b0576448445f2276f3/.claude/commands/kiro/requirements.md", "key": "yamat47/project-boilerplate/.claude/commands/kiro/requirements.md" } } }

requirements

About