[IMPORTANT] Use

TaskCreate

to break ALL work into small tasks BEFORE starting — including tasks for each file read. This prevents context loss from long files. For simple tasks, AI MUST ask user whether to skip.

MANDATORY IMPORTANT MUST Plan ToDo Task to READ the following project-specific reference doc:

• project-structure-reference.md

  -- project patterns and structure

• docs/project-reference/domain-entities-reference.md

  — Domain entity catalog, relationships, cross-service sync (read when task involves business entities/models)

If file not found, search for: project documentation, coding standards, architecture docs.

1. Idea Capture — Structure raw concepts with module detection and domain context
2. Backlog Management — Create/refine PBIs, track dependencies
3. Prioritization — Apply RICE score, MoSCoW, or Value/Effort matrix
4. Validation — MANDATORY interview to confirm assumptions before completion

• Use numeric priority ordering (1-999), never High/Medium/Low categories
• Always detect project module and load feature context for domain ideas
• Post-refinement validation interview is NOT optional
• Use domain-specific entity names (Candidate, Employee, Goal, etc.)

1. Run:

   Glob("docs/business-features/*/README.md")

2. Extract module names from paths
3. Match keywords using

   .claude/skills/shared/module-detection-keywords.md

• Auto-detect module(s) without displaying confidence levels
• Only prompt when ambiguous: "Which project module is this for?" + list Glob results

1. Read

   docs/business-features/{module}/README.md

   (first 200 lines for overview)
2. Extract feature list from Quick Navigation
3. Identify closest matching feature(s)
4. Note related entities and services

• ServiceA: Candidate (not "Applicant"), Job, JobApplication, Interview, CV
• ServiceB: Order, Feedback, Review, CheckIn, Report
• Use "Employee" not "User" for staff members
• Use "Candidate" not "Applicant" for recruitment

• Module README overview: ~2K tokens
• Full feature doc sections: 3-5K tokens per feature
• Multi-module: Load all detected (may increase total)

• Transform raw concepts into structured idea artifacts
• Identify problem statements and value propositions
• Tag and categorize for future refinement
• NEW: Detect module and inject feature context

• Create and refine Product Backlog Items (PBIs)
• Maintain backlog ordering (not categories)
• Track dependencies and blockers

• Must Have: Critical for release, non-negotiable
• Should Have: Important but not vital
• Could Have: Nice to have, low effort
• Won't Have: Out of scope this cycle

• Capacity planning based on velocity
• Sprint goal definition
• Commitment vs forecast distinction

• Idea:

  .claude/docs/team-artifacts/templates/idea-template.md

• PBI:

  .claude/docs/team-artifacts/templates/pbi-template.md

1. Use

   /idea

   command workflow
2. Detect module from conversation keywords
3. Load feature context from docs/business-features/
4. Populate idea-template.md with domain fields
5. Save to

   team-artifacts/ideas/

6. Suggest next step:

   /refine {idea-file}

1. Read all PBIs in

   team-artifacts/pbis/

2. Apply requested framework (RICE, MoSCoW, Value/Effort)
3. Output ordered list with scores
4. Update priority field in PBI frontmatter

• Numeric ordering: 1 (highest) to 999 (lowest)
• Never use High/Medium/Low categories

1. Category-based priority - Use ordered sequence, not High/Med/Low
2. Vague acceptance criteria - Require GIVEN/WHEN/THEN format
3. Scope creep - Explicitly list "Out of Scope"
4. Missing dependencies - Always identify upstream/downstream
5. Generic terminology - Use domain-specific entity names

• Velocity: {points}
• Commitment: {%}

undefined

• Problem statement is user-focused, not solution-focused
• Value proposition quantified or qualified
• Priority has numeric order
• Dependencies explicitly listed
• Status frontmatter current
• Module detected and context loaded (if domain-related)
• Domain vocabulary used correctly

1. Confirm assumptions about user needs
2. Verify scope boundaries
3. Surface potential concerns
4. Brainstorm alternatives

• {decision}: {user choice}

• {concern}: {resolution}

• {follow-up if any}

undefined

• Priority conflicts with roadmap
• Resource constraints identified
• Stakeholder alignment needed
• Cross-team dependency discovered

• business-analyst

• project-manager

• Always plan and break work into many small todo tasks
• Always add a final review todo task to verify work quality and identify fixes/enhancements