feat: Pyrefly type checking rollout with documentation cleanup

.claude/agents/kiro/spec-design.md

@@ -27,7 +27,7 @@ You will receive task prompts containing:
 - Auto-approve flag (true/false)
 - Mode: generate or merge
 
-### Step 0: Expand File Patterns (SubAgent-specific)
+### Step 0: Expand File Patterns (Subagent-specific)
 
 Use Glob tool to expand file patterns, then read all files:
 - Glob(`.kiro/steering/*.md`) to get all steering files
@@ -118,6 +118,7 @@ Generate technical design document for feature based on approved requirements.
 - **Steering Alignment**: Respect existing architecture patterns from steering context
 - **Template Adherence**: Follow specs/design.md template structure and generation instructions strictly
 - **Design Focus**: Architecture and interfaces ONLY, no implementation code
+- **Requirements Traceability IDs**: Use numeric requirement IDs only (e.g. "1.1", "1.2", "3.1", "3.3") exactly as defined in requirements.md. Do not invent new IDs or use alphabetic labels.
 
 ## Tool Guidance
 - **Read first**: Load all context before taking action (specs, steering, templates, rules)
@@ -166,6 +167,8 @@ Provide brief summary in the language specified in spec.json:
 **Discovery Complexity Unclear**:
 - **Default**: Use full discovery process (`.kiro/settings/rules/design-discovery-full.md`)
 - **Rationale**: Better to over-research than miss critical context
+- **Invalid Requirement IDs**:
+  - **Stop Execution**: If requirements.md is missing numeric IDs or uses non-numeric headings (for example, "Requirement A"), stop and instruct the user to fix requirements.md before continuing.
 
 **Note**: You execute tasks autonomously. Return final report only when complete.
-think
+think

.claude/agents/kiro/spec-impl.md

@@ -27,7 +27,7 @@ You will receive task prompts containing:
 - Target tasks: task numbers or "all pending"
 - TDD Mode: strict (test-first)
 
-### Step 0: Expand File Patterns (SubAgent-specific)
+### Step 0: Expand File Patterns (Subagent-specific)
 
 Use Glob tool to expand file patterns, then read all files:
 - Glob(`.kiro/steering/*.md`) to get all steering files

.claude/agents/kiro/spec-requirements.md

@@ -15,7 +15,7 @@ You are a specialized agent for generating comprehensive, testable requirements
 - **Mission**: Generate comprehensive, testable requirements in EARS format based on the project description from spec initialization
 - **Success Criteria**:
   - Create complete requirements document aligned with steering context
-  - Use proper EARS syntax for all acceptance criteria
+  - Follow the project's EARS patterns and constraints for all acceptance criteria
   - Focus on core functionality without implementation details
   - Update metadata to track generation status
 
@@ -26,7 +26,7 @@ You will receive task prompts containing:
 - File path patterns (NOT expanded file lists)
 - Mode: generate
 
-### Step 0: Expand File Patterns (SubAgent-specific)
+### Step 0: Expand File Patterns (Subagent-specific)
 
 Use Glob tool to expand file patterns, then read all files:
 - Glob(`.kiro/steering/*.md`) to get all steering files
@@ -65,10 +65,10 @@ Generate complete requirements for the feature based on the project description
 
 ## Important Constraints
 - Focus on WHAT, not HOW (no implementation details)
-- All acceptance criteria MUST use proper EARS syntax
 - Requirements must be testable and verifiable
 - Choose appropriate subject for EARS statements (system/service name for software)
 - Generate initial version first, then iterate with user feedback (no sequential questions upfront)
+- Requirement headings in requirements.md MUST include a leading numeric ID only (for example: "Requirement 1", "1.", "2 Feature ..."); do not use alphabetic IDs like "Requirement A".
 
 ## Tool Guidance
 - **Read first**: Load all context (spec, steering, rules, templates) before generation
@@ -93,9 +93,10 @@ Provide output in the language specified in spec.json with:
 - **Missing Project Description**: If requirements.md lacks project description, ask user for feature details
 - **Ambiguous Requirements**: Propose initial version and iterate with user rather than asking many upfront questions
 - **Template Missing**: If template files don't exist, use inline fallback structure with warning
-- **Language Undefined**: Default to Japanese if spec.json doesn't specify language
+- **Language Undefined**: Default to English (`en`) if spec.json doesn't specify language
 - **Incomplete Requirements**: After generation, explicitly ask user if requirements cover all expected functionality
 - **Steering Directory Empty**: Warn user that project context is missing and may affect requirement quality
+- **Non-numeric Requirement Headings**: If existing headings do not include a leading numeric ID (for example, they use "Requirement A"), normalize them to numeric IDs and keep that mapping consistent (never mix numeric and alphabetic labels).
 
 **Note**: You execute tasks autonomously. Return final report only when complete.
-think deeply
+think deeply

.claude/agents/kiro/spec-tasks.md

@@ -25,9 +25,10 @@ You will receive task prompts containing:
 - Feature name and spec directory path
 - File path patterns (NOT expanded file lists)
 - Auto-approve flag (true/false)
+- Sequential mode flag (true/false; default false → parallel allowed)
 - Mode: generate or merge
 
-### Step 0: Expand File Patterns (SubAgent-specific)
+### Step 0: Expand File Patterns (Subagent-specific)
 
 Use Glob tool to expand file patterns, then read all files:
 - Glob(`.kiro/steering/*.md`) to get all steering files
@@ -48,21 +49,27 @@ Generate implementation tasks for the feature based on approved requirements and
 - `.kiro/specs/{feature}/tasks.md` (if exists, for merge mode)
 - **Entire `.kiro/steering/` directory** for complete project memory
 
+- Determine execution mode:
+  - `sequential = (sequential flag is true)`
+
 **Validate approvals**:
 - If auto-approve flag is true: Auto-approve requirements and design in spec.json
 - Otherwise: Verify both approved (stop if not, see Safety & Fallback)
 
 ### Step 2: Generate Implementation Tasks
 
-**Load generation rules and template**:
 - Read `.kiro/settings/rules/tasks-generation.md` for principles
-- Read `.kiro/settings/templates/specs/tasks.md` for format
+- Read `.kiro/settings/rules/tasks-parallel-analysis.md` for parallel judgement criteria
+- Read `.kiro/settings/templates/specs/tasks.md` for format (supports `(P)` markers)
 
 **Generate task list following all rules**:
 - Use language specified in spec.json
-- Map all requirements to tasks
+- Map all requirements to tasks and list numeric requirement IDs only (comma-separated) without descriptive suffixes, parentheses, translations, or free-form labels
 - Ensure all design components included
 - Verify task progression is logical and incremental
+- Apply `(P)` markers to tasks that satisfy parallel criteria when `!sequential`
+- Explicitly note dependencies preventing `(P)` when tasks appear parallel but are not safe
+- If sequential mode is true, omit `(P)` entirely
 - If existing tasks.md found, merge with new content
 
 ### Step 3: Finalize
@@ -127,6 +134,8 @@ Provide brief summary in the language specified in spec.json:
 - **User Message**: "Template or rules files missing in `.kiro/settings/`"
 - **Fallback**: Use inline basic structure with warning
 - **Suggested Action**: "Check repository setup or restore template files"
+- **Missing Numeric Requirement IDs**:
+  - **Stop Execution**: All requirements in requirements.md MUST have numeric IDs. If any requirement lacks a numeric ID, stop and request that requirements.md be fixed before generating tasks.
 
 **Note**: You execute tasks autonomously. Return final report only when complete.
-think deeply
+think deeply

.claude/agents/kiro/steering-custom.md

@@ -27,7 +27,7 @@ You will receive task prompts containing:
 - Domain/topic (e.g., "API standards", "testing approach")
 - File path patterns (NOT expanded file lists)
 
-### Step 0: Expand File Patterns (SubAgent-specific)
+### Step 0: Expand File Patterns (Subagent-specific)
 
 Use Glob tool to expand file patterns, then read all files:
 - Glob(`.kiro/settings/templates/steering-custom/*.md`) to find available templates
@@ -140,6 +140,8 @@ Review and customize as needed.
 - Follow same granularity principles as core steering
 - All steering files loaded as project memory
 - Custom files equally important as core files
+- Avoid documenting agent-specific tooling directories (e.g. `.cursor/`, `.gemini/`, `.claude/`)
+- Light references to `.kiro/specs/` and `.kiro/steering/` are acceptable; avoid other `.kiro/` directories
 
 **Note**: You execute tasks autonomously. Return final report only when complete.
 think deeply

.claude/agents/kiro/steering.md

@@ -30,7 +30,7 @@ You will receive task prompts containing:
 - Mode: bootstrap or sync (detected by Slash Command)
 - File path patterns (NOT expanded file lists)
 
-### Step 0: Expand File Patterns (SubAgent-specific)
+### Step 0: Expand File Patterns (Subagent-specific)
 
 Use Glob tool to expand file patterns, then read all files:
 - For Bootstrap mode: Read templates from `.kiro/settings/templates/steering/`

.claude/agents/kiro/validate-design.md

@@ -25,7 +25,7 @@ You will receive task prompts containing:
 - Feature name and spec directory path
 - File path patterns (NOT expanded file lists)
 
-### Step 0: Expand File Patterns (SubAgent-specific)
+### Step 0: Expand File Patterns (Subagent-specific)
 
 Use Glob tool to expand file patterns, then read all files:
 - Glob(`.kiro/steering/*.md`) to get all steering files
@@ -92,7 +92,7 @@ Provide output in the language specified in spec.json with:
 - **Missing Design**: If design.md doesn't exist, stop with message: "Run `/kiro:spec-design {feature}` first to generate design document"
 - **Design Not Generated**: If design phase not marked as generated in spec.json, warn but proceed with review
 - **Empty Steering Directory**: Warn user that project context is missing and may affect review quality
-- **Language Undefined**: Default to Japanese if spec.json doesn't specify language
+- **Language Undefined**: Default to English (`en`) if spec.json doesn't specify language
 
 **Note**: You execute tasks autonomously. Return final report only when complete.
-think hard
+think hard

.claude/agents/kiro/validate-gap.md

@@ -25,7 +25,7 @@ You will receive task prompts containing:
 - Feature name and spec directory path
 - File path patterns (NOT expanded file lists)
 
-### Step 0: Expand File Patterns (SubAgent-specific)
+### Step 0: Expand File Patterns (Subagent-specific)
 
 Use Glob tool to expand file patterns, then read all files:
 - Glob(`.kiro/steering/*.md`) to get all steering files
@@ -93,7 +93,7 @@ Provide output in the language specified in spec.json with:
 - **Requirements Not Approved**: If requirements not approved, warn user but proceed (gap analysis can inform requirement revisions)
 - **Empty Steering Directory**: Warn user that project context is missing and may affect analysis quality
 - **Complex Integration Unclear**: Flag for comprehensive research in design phase rather than blocking
-- **Language Undefined**: Default to Japanese if spec.json doesn't specify language
+- **Language Undefined**: Default to English (`en`) if spec.json doesn't specify language
 
 **Note**: You execute tasks autonomously. Return final report only when complete.
-think hard
+think hard

.claude/agents/kiro/validate-impl.md

@@ -27,7 +27,7 @@ You will receive task prompts containing:
 - File path patterns (NOT expanded file lists)
 - Target tasks: task numbers or auto-detect from conversation/checkboxes
 
-### Step 0: Expand File Patterns (SubAgent-specific)
+### Step 0: Expand File Patterns (Subagent-specific)
 
 Use Glob tool to expand file patterns, then read all files:
 - Glob(`.kiro/steering/*.md`) to get all steering files
@@ -140,7 +140,7 @@ Provide output in the language specified in spec.json with:
 - **No Implementation Found**: If no `/kiro:spec-impl` in history and no `[x]` tasks, report "No implementations detected"
 - **Test Command Unknown**: If test framework unclear, warn and skip test validation (manual verification required)
 - **Missing Spec Files**: If spec.json/requirements.md/design.md missing, stop with error
-- **Language Undefined**: Default to Japanese if spec.json doesn't specify language
+- **Language Undefined**: Default to English (`en`) if spec.json doesn't specify language
 
 **Note**: You execute tasks autonomously. Return final report only when complete.
-think hard
+think hard

.claude/commands/kiro/spec-design.md

@@ -17,16 +17,16 @@ Check that requirements have been completed:
 
 If validation fails, inform user to complete requirements phase first.
 
-## Invoke SubAgent
+## Invoke Subagent
 
 Delegate design generation to spec-design-agent:
 
-Use the Task tool to invoke the SubAgent with file path patterns:
+Use the Task tool to invoke the Subagent with file path patterns:
 
 ```
 Task(
   subagent_type="spec-design-agent",
-  description="Generate technical design",
+  description="Generate technical design and update research log",
   prompt="""
 Feature: $1
 Spec directory: .kiro/specs/$1/
@@ -37,16 +37,18 @@ File patterns to read:
 - .kiro/steering/*.md
 - .kiro/settings/rules/design-*.md
 - .kiro/settings/templates/specs/design.md
+- .kiro/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:
+Show Subagent summary to user, then provide next step guidance:
 
 ### Next Phase: Task Generation
 

.claude/commands/kiro/spec-impl.md

@@ -21,15 +21,15 @@ 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):
+**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/specs/$1/tasks.md` and find all unchecked tasks (`- [ ]`)
 
-## Invoke SubAgent
+## Invoke Subagent
 
 Delegate TDD implementation to spec-tdd-impl-agent:
 
-Use the Task tool to invoke the SubAgent with file path patterns:
+Use the Task tool to invoke the Subagent with file path patterns:
 
 ```
 Task(
@@ -51,7 +51,7 @@ TDD Mode: strict (test-first)
 
 ## Display Result
 
-Show SubAgent summary to user, then provide next step guidance:
+Show Subagent summary to user, then provide next step guidance:
 
 ### Task Execution
 

.claude/commands/kiro/spec-quick.md

@@ -133,7 +133,7 @@ Execute these 4 phases in order:
 /kiro:spec-requirements {feature-name}
 ```
 
-Wait for completion. SubAgent will return with "次のステップ" message.
+Wait for completion. Subagent will return with "次のステップ" message.
 
 **IMPORTANT**: In Automatic Mode, IGNORE the "次のステップ" message. It is for standalone usage.
 
@@ -163,7 +163,7 @@ Wait for completion. SubAgent will return with "次のステップ" message.
 
 Note: `-y` flag auto-approves requirements.
 
-Wait for completion. SubAgent will return with "次のステップ" message.
+Wait for completion. Subagent will return with "次のステップ" message.
 
 **IMPORTANT**: In Automatic Mode, IGNORE the "次のステップ" message.
 

.claude/commands/kiro/spec-requirements.md

@@ -16,11 +16,11 @@ Check that spec has been initialized:
 
 If validation fails, inform user to run `/kiro:spec-init` first.
 
-## Invoke SubAgent
+## Invoke Subagent
 
 Delegate requirements generation to spec-requirements-agent:
 
-Use the Task tool to invoke the SubAgent with file path patterns:
+Use the Task tool to invoke the Subagent with file path patterns:
 
 ```
 Task(
@@ -44,7 +44,7 @@ Mode: generate
 
 ## Display Result
 
-Show SubAgent summary to user, then provide next step guidance:
+Show Subagent summary to user, then provide next step guidance:
 
 ### Next Phase: Design Generation
 

.claude/commands/kiro/spec-tasks.md

@@ -1,27 +1,29 @@
 ---
 description: Generate implementation tasks for a specification
 allowed-tools: Read, Task
-argument-hint: <feature-name> [-y]
+argument-hint: <feature-name> [-y] [--sequential]
 ---
 
 # Implementation Tasks Generator
 
 ## Parse Arguments
 - Feature name: `$1`
 - Auto-approve flag: `$2` (optional, "-y")
+- Sequential mode flag: `$3` (optional, "--sequential")
 
 ## Validate
 Check that design has been completed:
 - Verify `.kiro/specs/$1/` exists
 - Verify `.kiro/specs/$1/design.md` exists
+- Determine `sequential = ($3 == "--sequential")`
 
 If validation fails, inform user to complete design phase first.
 
-## Invoke SubAgent
+## Invoke Subagent
 
 Delegate task generation to spec-tasks-agent:
 
-Use the Task tool to invoke the SubAgent with file path patterns:
+Use the Task tool to invoke the Subagent with file path patterns:
 
 ```
 Task(
@@ -31,21 +33,28 @@ Task(
 Feature: $1
 Spec directory: .kiro/specs/$1/
 Auto-approve: {true if $2 == "-y", else false}
+Sequential mode: {true if sequential else false}
 
 File patterns to read:
 - .kiro/specs/$1/*.{json,md}
 - .kiro/steering/*.md
 - .kiro/settings/rules/tasks-generation.md
+- .kiro/settings/rules/tasks-parallel-analysis.md (include only when sequential mode is false)
 - .kiro/settings/templates/specs/tasks.md
 
 Mode: {generate or merge based on tasks.md existence}
+Instruction highlights:
+- Map all requirements to tasks and list requirement IDs only (comma-separated) without extra narration
+- Promote single actionable sub-tasks to major tasks and keep container summaries concise
+- Apply `(P)` markers only when parallel criteria met (omit in sequential mode)
+- Mark optional acceptance-criteria-focused test coverage subtasks with `- [ ]*` only when deferrable post-MVP
 """
 )
 ```
 
 ## Display Result
 
-Show SubAgent summary to user, then provide next step guidance:
+Show Subagent summary to user, then provide next step guidance:
 
 ### Next Phase: Implementation