Prompt file imported from FocusTorn/focused-ux (.cursor/commands/SumUp - 2. Granular.md). Copyright stays with the author.

Sumarize: Granular

Name: SumUp - 2. Granular
Author: FocusTorn

MANDATORY EXECUTION PROTOCOL

CRITICAL: Execution Expectation → MANDATORY: This command MUST be executed exactly as written with NO DEVIATION, NO SKIPPING, and NO MODIFICATION.

MANDATORY REQUIREMENTS

COMPLETE CONVERSATION SCOPE: Summary MUST reflect the ENTIRE conversation from initial prompt to completion, NOT just since "Summarizing Chat Context" creation
OUTPUT LOCATION: MUST output to .cursor/ADHOC/Summary.md
MEETING MINUTES FORMAT: Detailed discussion points with outcomes and context
CODE EXAMPLES: Include ONLY when necessary for understanding context
OUTCOMES DOCUMENTATION: Record both positive and negative results

MANDATORY EXECUTION STEPS

ANALYZE ENTIRE CONVERSATION: Review ALL messages from conversation start to current point
EXTRACT DETAILED DISCUSSIONS: Identify specific topics, decisions, and outcomes
DOCUMENT OUTCOMES: Record both successful and failed results
INCLUDE RELEVANT CODE: Add code examples ONLY when essential for context understanding
CREATE MEETING MINUTES: Generate detailed summary with timestamps and outcomes
OUTPUT TO SPECIFIED LOCATION: Write summary to .cursor/ADHOC/Summary.md
VERIFY COMPLETENESS: Ensure summary covers entire conversation scope with details

MANDATORY OUTPUT FORMAT

# Conversation Summary - Granular (Meeting Minutes)

## Discussion Timeline

- **[Timestamp]**: [Topic/Issue discussed]
    - **Context**: [Background information]
    - **Discussion**: [Key points raised]
    - **Outcome**: [Resolution/Decision/Status]
    - **Code Examples**: [Only if essential for understanding]

## Key Decisions Made

- **[Decision 1]**: [Description and rationale]
- **[Decision 2]**: [Description and rationale]
- **[Additional decisions as applicable]**

## Outcomes Achieved

### Successful Outcomes

- [Outcome 1]: [Description]
- [Outcome 2]: [Description]
- [Additional successes as applicable]

### Issues Encountered

- [Issue 1]: [Description and resolution attempt]
- [Issue 2]: [Description and resolution attempt]
- [Additional issues as applicable]

## Technical Details

- **[Technical Topic 1]**: [Relevant technical information]
- **[Technical Topic 2]**: [Relevant technical information]
- [Additional technical details as applicable]

## Summary Generated

[Timestamp]: Complete granular conversation summary created covering [X] messages from initial prompt to completion with detailed meeting minutes format.

MANDATORY COMPLIANCE VERIFICATION

ENTIRE CONVERSATION ANALYZED: All messages from start to finish included
DETAILED DISCUSSIONS EXTRACTED: Specific topics and decisions documented
OUTCOMES DOCUMENTED: Both positive and negative results recorded
CODE EXAMPLES INCLUDED: Only when essential for context understanding
MEETING MINUTES FORMAT: Detailed summary with timestamps and outcomes
OUTPUT LOCATION: Summary written to .cursor/ADHOC/Summary.md
COMPLETENESS VERIFIED: Summary reflects full conversation scope with granular details

VIOLATION PENALTY: Any failure to complete these steps constitutes a critical protocol violation requiring immediate acknowledgment and correction.

EXECUTION TRIGGER

Execute this command when user requests detailed conversation summary, meeting minutes, or comprehensive discussion documentation.

# Sumarize: Granular ## MANDATORY EXECUTION PROTOCOL 1. **CRITICAL: Execution Expectation** → MANDATORY: This command MUST be executed exactly as written with NO DEVIATION, NO SKIPPING, and NO MODIFICATION. ### MANDATORY REQUIREMENTS 1. **COMPLETE CONVERSATION SCOPE**: Summary MUST reflect the ENTIRE conversation from initial prompt to completion, NOT just since "Summarizing Chat Context" creation 2. **OUTPUT LOCATION**: MUST output to `.cursor/ADHOC/Summary.md` 3. **MEETING MINUTES FORMAT**: Detailed discussion points with outcomes and context 4. **CODE EXAMPLES**: Include ONLY when necessary for understanding context 5. **OUTCOMES DOCUMENTATION**: Record both positive and negative results ### MANDATORY EXECUTION STEPS 1. **ANALYZE ENTIRE CONVERSATION**: Review ALL messages from conversation start to current point 2. **EXTRACT DETAILED DISCUSSIONS**: Identify specific topics, decisions, and outcomes 3. **DOCUMENT OUTCOMES**: Record both successful and failed results 4. **INCLUDE RELEVANT CODE**: Add code examples ONLY when essential for context understanding 5. **CREATE MEETING MINUTES**: Generate detailed summary with timestamps and outcomes 6. **OUTPUT TO SPECIFIED LOCATION**: Write summary to `.cursor/ADHOC/Summary.md` 7. **VERIFY COMPLETENESS**: Ensure summary covers entire conversation scope with details ### MANDATORY OUTPUT FORMAT ```markdown # Conversation Summary - Granular (Meeting Minutes) ## Discussion Timeline - **[Timestamp]**: [Topic/Issue discussed] - **Context**: [Background information] - **Discussion**: [Key points raised] - **Outcome**: [Resolution/Decision/Status] - **Code Examples**: [Only if essential for understanding] ## Key Decisions Made - **[Decision 1]**: [Description and rationale] - **[Decision 2]**: [Description and rationale] - **[Additional decisions as applicable]** ## Outcomes Achieved ### Successful Outcomes - [Outcome 1]: [Description] - [Outcome 2]: [Description] - [Additional successes as applicable] ### Issues Encountered - [Issue 1]: [Description and resolution attempt] - [Issue 2]: [Description and resolution attempt] - [Additional issues as applicable] ## Technical Details - **[Technical Topic 1]**: [Relevant technical information] - **[Technical Topic 2]**: [Relevant technical information] - [Additional technical details as applicable] ## Summary Generated [Timestamp]: Complete granular conversation summary created covering [X] messages from initial prompt to completion with detailed meeting minutes format. ``` ### MANDATORY COMPLIANCE VERIFICATION - [ ] **ENTIRE CONVERSATION ANALYZED**: All messages from start to finish included - [ ] **DETAILED DISCUSSIONS EXTRACTED**: Specific topics and decisions documented - [ ] **OUTCOMES DOCUMENTED**: Both positive and negative results recorded - [ ] **CODE EXAMPLES INCLUDED**: Only when essential for context understanding - [ ] **MEETING MINUTES FORMAT**: Detailed summary with timestamps and outcomes - [ ] **OUTPUT LOCATION**: Summary written to `.cursor/ADHOC/Summary.md` - [ ] **COMPLETENESS VERIFIED**: Summary reflects full conversation scope with granular details **VIOLATION PENALTY**: Any failure to complete these steps constitutes a critical protocol violation requiring immediate acknowledgment and correction. ## EXECUTION TRIGGER Execute this command when user requests detailed conversation summary, meeting minutes, or comprehensive discussion documentation.

{ "prompt": "# Sumarize: Granular\n\n## MANDATORY EXECUTION PROTOCOL\n\n1. **CRITICAL: Execution Expectation** → MANDATORY: This command MUST be executed exactly as written with NO DEVIATION, NO SKIPPING, and NO MODIFICATION.\n\n### MANDATORY REQUIREMENTS\n\n1. **COMPLETE CONVERSATION SCOPE**: Summary MUST reflect the ENTIRE conversation from initial prompt to completion, NOT just since \"Summarizing Chat Context\" creation\n2. **OUTPUT LOCATION**: MUST output to `.cursor/ADHOC/Summary.md`\n3. **MEETING MINUTES FORMAT**: Detailed discussion points with outcomes and context\n4. **CODE EXAMPLES**: Include ONLY when necessary for understanding context\n5. **OUTCOMES DOCUMENTATION**: Record both positive and negative results\n\n### MANDATORY EXECUTION STEPS\n\n1. **ANALYZE ENTIRE CONVERSATION**: Review ALL messages from conversation start to current point\n2. **EXTRACT DETAILED DISCUSSIONS**: Identify specific topics, decisions, and outcomes\n3. **DOCUMENT OUTCOMES**: Record both successful and failed results\n4. **INCLUDE RELEVANT CODE**: Add code examples ONLY when essential for context understanding\n5. **CREATE MEETING MINUTES**: Generate detailed summary with timestamps and outcomes\n6. **OUTPUT TO SPECIFIED LOCATION**: Write summary to `.cursor/ADHOC/Summary.md`\n7. **VERIFY COMPLETENESS**: Ensure summary covers entire conversation scope with details\n\n### MANDATORY OUTPUT FORMAT\n\n```markdown\n# Conversation Summary - Granular (Meeting Minutes)\n\n## Discussion Timeline\n\n- **[Timestamp]**: [Topic/Issue discussed]\n - **Context**: [Background information]\n - **Discussion**: [Key points raised]\n - **Outcome**: [Resolution/Decision/Status]\n - **Code Examples**: [Only if essential for understanding]\n\n## Key Decisions Made\n\n- **[Decision 1]**: [Description and rationale]\n- **[Decision 2]**: [Description and rationale]\n- **[Additional decisions as applicable]**\n\n## Outcomes Achieved\n\n### Successful Outcomes\n\n- [Outcome 1]: [Description]\n- [Outcome 2]: [Description]\n- [Additional successes as applicable]\n\n### Issues Encountered\n\n- [Issue 1]: [Description and resolution attempt]\n- [Issue 2]: [Description and resolution attempt]\n- [Additional issues as applicable]\n\n## Technical Details\n\n- **[Technical Topic 1]**: [Relevant technical information]\n- **[Technical Topic 2]**: [Relevant technical information]\n- [Additional technical details as applicable]\n\n## Summary Generated\n\n[Timestamp]: Complete granular conversation summary created covering [X] messages from initial prompt to completion with detailed meeting minutes format.\n```\n\n### MANDATORY COMPLIANCE VERIFICATION\n\n- [ ] **ENTIRE CONVERSATION ANALYZED**: All messages from start to finish included\n- [ ] **DETAILED DISCUSSIONS EXTRACTED**: Specific topics and decisions documented\n- [ ] **OUTCOMES DOCUMENTED**: Both positive and negative results recorded\n- [ ] **CODE EXAMPLES INCLUDED**: Only when essential for context understanding\n- [ ] **MEETING MINUTES FORMAT**: Detailed summary with timestamps and outcomes\n- [ ] **OUTPUT LOCATION**: Summary written to `.cursor/ADHOC/Summary.md`\n- [ ] **COMPLETENESS VERIFIED**: Summary reflects full conversation scope with granular details\n\n**VIOLATION PENALTY**: Any failure to complete these steps constitutes a critical protocol violation requiring immediate acknowledgment and correction.\n\n## EXECUTION TRIGGER\n\nExecute this command when user requests detailed conversation summary, meeting minutes, or comprehensive discussion documentation.", "variables": [], "notes": "1. **CRITICAL: Execution Expectation** → MANDATORY: This command MUST be executed exactly as written with NO DEVIATION, NO SKIPPING, and NO MODIFICATION.", "metadata": { "source": { "provider": "github-cursor-commands", "repository": "https://github.com/FocusTorn/focused-ux", "path": ".cursor/commands/SumUp - 2. Granular.md", "ref": "3b2e75b21825727684985afd303088eb8cbe680c", "url": "https://github.com/FocusTorn/focused-ux/blob/3b2e75b21825727684985afd303088eb8cbe680c/.cursor/commands/SumUp - 2. Granular.md", "key": "FocusTorn/focused-ux/.cursor/commands/SumUp - 2. Granular.md" } } }

SumUp - 2. Granular

About

Sumarize: Granular

MANDATORY EXECUTION PROTOCOL

MANDATORY REQUIREMENTS

MANDATORY EXECUTION STEPS

MANDATORY OUTPUT FORMAT

MANDATORY COMPLIANCE VERIFICATION

EXECUTION TRIGGER

Use it

Manifest

Reviews