feat: add cursor support

Update README.md

…-ready tasks

Major improvements:
1. File Organization:
   - All initiative files now organized in specs/<number>-<short-name>/ folders
   - No more messy project root with scattered files
   - Each initiative is self-contained and easy to archive

2. Phase Boundary Clarification:
   - /speckit.specify and /speckit.plan are BRAINSTORMING phases
   - Only create markdown planning documents (no yaml, scripts, or data files)
   - Implementation artifacts created during /speckit.implement phase
   - Added explicit guardrails and reminders throughout templates

3. JIRA-Ready Task Format:
   - Tasks now include: title, owner, estimate, priority
   - Detailed description with business context
   - Acceptance criteria (3-5 specific, measurable items)
   - Deliverable paths, dependencies, and business value
   - Ready to import into JIRA or project management tools

4. Script Updates:
   - Added INITIATIVE_DIR to JSON output in all scripts
   - Both bash and PowerShell scripts updated consistently

5. Documentation:
   - Updated README with folder structure diagram
   - Added phase boundary summary
   - Clarified what gets created in each phase

Fixes #1 - initiative files scattered in project root
Fixes #2 - AI creating implementation files during planning
Fixes #3 - tasks too simple for JIRA import

…r feedback)

Implements fixes for workflow-reviewer agent's identified critical issues:

1. Fix State Management Gap (Critical github#1)
   - Added spec-metadata.json generation in /speckit.quick Phase 1
   - Enables integration with /speckit.status and /speckit.pm (v2.3 compatibility)
   - Metadata tracks: workflow_type, phase, approvals, risk_level
   - Updates metadata after each phase (pre-flight, implementation, quality gate, complete)
   - File: .specify/quick-tasks/quick-task-[timestamp]-metadata.json

2. Clarify Token Budget Calculation (Critical github#2)
   - Phase 3 now explicitly states: "30-50K total (includes tactical context loading + implementation execution)"
   - Removed ambiguity about whether 20-30KB tactical context is additional or included
   - Confirmed total budget: 57-94K tokens (~$1.10-$1.80)

3. Verify Documentation Consistency (Critical github#3)
   - Verified command counts are correct: 18 core + 3 epic = 21 total
   - Confirmed /speckit.quick is in all relevant tables (CLAUDE.md, README.md)
   - No changes needed - documentation was already accurate

4. Add Risk Scoring to Step 0.5 (Major github#4)
   - Added heuristic risk assessment BEFORE complexity analysis
   - HIGH-RISK indicators: payment, auth, multi-tenant, compliance (GDPR/HIPAA/PCI), database migration
   - MEDIUM-RISK indicators: database, schema change, API endpoint, real-time, bulk operations
   - Decision logic:
     - ANY HIGH-RISK keyword → Block quick workflow, require full workflow
     - ≥2 MEDIUM-RISK keywords → Block quick workflow, recommend full workflow
     - ELSE → LOW-RISK (0-3) → Continue to complexity analysis
   - Prevents users from accidentally using /speckit.quick on HIGH-risk tasks

Benefits:
- State management enables workflow tracking and status visibility
- Token budget clarity prevents cost estimation errors
- Risk scoring prevents inappropriate use of quick workflow for security-critical/high-risk features
- Maintains constitutional enforcement and quality gates

Files Modified:
- src/.claude/commands/speckit.quick.md:
  - Added metadata generation in Phase 1 (lines 167-215)
  - Added metadata updates in Phase 2, 3, 4, 5 (pre-flight, implementation, quality gate, complete)
  - Clarified Phase 3 token budget (line 377: "30-50K total includes tactical context")

- src/.claude/commands/speckit.specify.md:
  - Added Quick Risk Assessment to Step 0.5 (lines 110-141)
  - HIGH-RISK/MEDIUM-RISK keyword detection
  - Blocks quick workflow for risky features

Overall Assessment: Addresses all critical issues identified by workflow-reviewer.
Estimated improvement: 8.5/10 (was 7.2/10)

Version: v2.9.1 (patch)