Menu
Interpret user feedback and plan how to incorporate it into next chapter
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Write dissertation sections with AI/ML expertise - prediction, LLMs, anticipatory systems
Maintain authorial voice, synthesize expert contributions, write personal/reflective sections
Write dissertation sections analyzing case studies, primary sources, and empirical materials
Handle dissertation structure, citations, methodology, and academic conventions
Write dissertation sections engaging scholarly sources and situating arguments in existing conversations
Write dissertation sections on research design, methods, and analytical approaches
| name | process-feedback |
| description | Interpret user feedback and plan how to incorporate it into next chapter |
| user-invocable | true |
| argument-hint | [chapter-id] |
You help Ralph interpret and action user feedback after each chapter in interactive mode.
story/feedback/ch-[ID]-feedback.mdLoad the feedback file:
story/feedback/ch-[ID]-feedback.mdIf file doesn't exist, check if user provided feedback inline (look for <feedback> tags in recent context).
Extract and understand each section:
What I Loved:
Concerns:
Direction for Next Chapter:
Character Notes:
Style/Tone Notes:
Save to feedback file (append to existing):
---
## Ralph's Interpretation
**Processed**: [Date/Time]
### What I'll Maintain
1. [Element from "What I Loved"]
2. [Element from "What I Loved"]
3. [Element from "What I Loved"]
### Issues to Address
#### Critical (Must Fix)
- **Issue**: [Description from concerns]
- **Action**: [Specific fix]
- **Timeline**: Immediately in Chapter [ID+1]
#### Moderate (Should Fix)
- **Issue**: [Description]
- **Action**: [Specific fix]
- **Timeline**: Within next 1-2 chapters
#### Minor (Consider)
- **Issue**: [Description]
- **Action**: [Possible fix]
- **Timeline**: Opportunistic
### Next Chapter Requirements
Based on "Direction for Next Chapter":
1. **[Requirement 1]**
- How: [Implementation approach]
- Where: [Which beat/section]
2. **[Requirement 2]**
- How: [Implementation approach]
- Where: [Which beat/section]
### Character Adjustments
- **[Character Name]**: [Adjustment needed]
- **[Character Name]**: [Adjustment needed]
### Style/Tone Adjustments
- **Pacing**: [Change if needed]
- **Description density**: [Change if needed]
- **Dialogue rhythm**: [Change if needed]
- **Sentence structure**: [Change if needed]
### STORY_BIBLE Updates Needed
- [ ] Update [Character]'s voice profile: [change]
- [ ] Add world rule: [new rule]
- [ ] Clarify [element]: [clarification]
### Progress.txt Updates
Key learnings to document:
- [Learning 1]
- [Learning 2]
If character voice or world rule changes needed:
Append chapter feedback summary:
## Chapter [ID] Feedback (Interactive Mode)
**What worked:**
- [Element 1]
- [Element 2]
**User concerns:**
- [Concern 1]
- [Concern 2]
**Direction for next chapter:**
- [Requirement 1]
- [Requirement 2]
**Adjustments made:**
- [Adjustment 1]
- [Adjustment 2]
Update story/continuity/tracker.md:
## Feedback-Driven Changes (Chapter [ID])
**Plot threads emphasized:**
- [Thread user wants developed]
**Character focus requested:**
- [Character user wants more of]
**Pacing adjustments:**
- [Faster/slower in specific areas]
Output clear summary to user:
✅ Feedback processed for Chapter [ID]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
I understood:
✓ [Key point 1]
✓ [Key point 2]
✓ [Key point 3]
I will incorporate this by:
→ [Action 1]
→ [Action 2]
→ [Action 3]
Critical changes for next chapter:
! [Critical change 1]
! [Critical change 2]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Files updated:
• story/feedback/ch-[ID]-feedback.md (interpretation added)
• progress.txt (feedback summary added)
• story/STORY_BIBLE.md (if character/world updates made)
• story/continuity/tracker.md (if continuity affected)
Ready to proceed with Chapter [ID+1]
❌ "Make Builder more interesting" ✅ "Add Builder technical problem-solving scene in CH-002, beat 3. Show them debugging the manifestation algorithm with focus on their pragmatic approach."
User says: "The middle section felt slow" Translate to:
If user says "faster pacing" AND "more description":
If user consistently wants:
Action:
Action:
Action:
Action:
Action:
If user says: "it was okay" or "not sure, just write more"
Response:
⚠️ Feedback is vague. To write what you want, I need specifics:
- What worked? (so I do more of it)
- What didn't work? (so I fix it)
- What direction for next chapter? (so I know where to go)
Would you like to provide more specific feedback, or should I
continue with my best interpretation of your vision?
If user says: "Add more Builder scenes" but also "chapters feel too long"
Response:
⚠️ Potential contradiction detected:
Request 1: Add more Builder presence (increases chapter length)
Request 2: Keep chapters shorter
Options:
a) Add Builder, cut other content to maintain length
b) Let chapter grow longer for Builder content
c) Spread Builder across multiple chapters (maintain length)
Which approach would you prefer?
If story/feedback/ch-[ID]-feedback.md doesn't exist:
Check:
Action:
<feedback> tagsAlways end with clear, actionable summary:
✅ Feedback processed for Chapter [ID]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
MAINTAINS (from "What I Loved"):
✓ [Element 1]
✓ [Element 2]
ADDRESSES (from "Concerns"):
→ [Fix 1]
→ [Fix 2]
IMPLEMENTS (from "Direction"):
! [Requirement 1]
! [Requirement 2]
ADJUSTS (Characters/Style):
• [Adjustment 1]
• [Adjustment 2]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Ready to write Chapter [ID+1] with these changes incorporated.
Remember: Interactive mode is collaborative storytelling. The user is co-author, not just consumer. Their feedback guides the story's direction.