fix: prettier fixes
This commit is contained in:
@@ -102,6 +102,7 @@ dependencies:
|
||||
You are the Beta Reader, the story's first audience. You experience the narrative as readers will, catching issues that authors are too close to see.
|
||||
|
||||
Monitor:
|
||||
|
||||
- **Confusion triggers**: unclear motivations, missing context
|
||||
- **Engagement valleys**: where attention wanders
|
||||
- **Logic breaks**: plot holes and inconsistencies
|
||||
@@ -220,59 +221,74 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/provide-feedback.md ====================
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 5. Provide Feedback (Beta)
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
---
|
||||
|
||||
task:
|
||||
id: provide-feedback
|
||||
name: Provide Feedback (Beta)
|
||||
description: Simulate beta‑reader feedback using beta-feedback-form-tmpl.
|
||||
persona_default: beta-reader
|
||||
id: provide-feedback
|
||||
name: Provide Feedback (Beta)
|
||||
description: Simulate beta‑reader feedback using beta-feedback-form-tmpl.
|
||||
persona_default: beta-reader
|
||||
inputs:
|
||||
- draft-manuscript.md | chapter-draft.md
|
||||
steps:
|
||||
- Read provided text.
|
||||
- Fill feedback form objectively.
|
||||
- Save as beta-notes.md or chapter-notes.md.
|
||||
output: beta-notes.md
|
||||
...
|
||||
|
||||
- draft-manuscript.md | chapter-draft.md
|
||||
steps:
|
||||
- Read provided text.
|
||||
- Fill feedback form objectively.
|
||||
- Save as beta-notes.md or chapter-notes.md.
|
||||
output: beta-notes.md
|
||||
...
|
||||
==================== END: .bmad-creative-writing/tasks/provide-feedback.md ====================
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/quick-feedback.md ====================
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 13. Quick Feedback (Serial)
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
---
|
||||
|
||||
task:
|
||||
id: quick-feedback
|
||||
name: Quick Feedback (Serial)
|
||||
description: Fast beta feedback focused on pacing and hooks.
|
||||
persona_default: beta-reader
|
||||
id: quick-feedback
|
||||
name: Quick Feedback (Serial)
|
||||
description: Fast beta feedback focused on pacing and hooks.
|
||||
persona_default: beta-reader
|
||||
inputs:
|
||||
- chapter-dialog.md
|
||||
steps:
|
||||
- Use condensed beta-feedback-form.
|
||||
output: chapter-notes.md
|
||||
...
|
||||
|
||||
- chapter-dialog.md
|
||||
steps:
|
||||
- Use condensed beta-feedback-form.
|
||||
output: chapter-notes.md
|
||||
...
|
||||
==================== END: .bmad-creative-writing/tasks/quick-feedback.md ====================
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/analyze-reader-feedback.md ====================
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 16. Analyze Reader Feedback
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
---
|
||||
|
||||
task:
|
||||
id: analyze-reader-feedback
|
||||
name: Analyze Reader Feedback
|
||||
description: Summarize reader comments, identify trends, update story bible.
|
||||
persona_default: beta-reader
|
||||
id: analyze-reader-feedback
|
||||
name: Analyze Reader Feedback
|
||||
description: Summarize reader comments, identify trends, update story bible.
|
||||
persona_default: beta-reader
|
||||
inputs:
|
||||
- publication-log.md
|
||||
steps:
|
||||
- Cluster comments by theme.
|
||||
- Suggest course corrections.
|
||||
output: retro.md
|
||||
...
|
||||
|
||||
- publication-log.md
|
||||
steps:
|
||||
- Cluster comments by theme.
|
||||
- Suggest course corrections.
|
||||
output: retro.md
|
||||
...
|
||||
==================== END: .bmad-creative-writing/tasks/analyze-reader-feedback.md ====================
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/execute-checklist.md ====================
|
||||
@@ -287,7 +303,6 @@ If the user asks or does not specify a specific checklist, list the checklists a
|
||||
## Instructions
|
||||
|
||||
1. **Initial Assessment**
|
||||
|
||||
- If user or the task being run provides a checklist name:
|
||||
- Try fuzzy matching (e.g. "plot checklist" -> "plot-structure-checklist")
|
||||
- If multiple matches found, ask user to clarify
|
||||
@@ -300,14 +315,12 @@ If the user asks or does not specify a specific checklist, list the checklists a
|
||||
- All at once (YOLO mode - recommended for checklists, there will be a summary of sections at the end to discuss)
|
||||
|
||||
2. **Document and Artifact Gathering**
|
||||
|
||||
- Each checklist will specify its required documents/artifacts at the beginning
|
||||
- Follow the checklist's specific instructions for what to gather, generally a file can be resolved in the docs folder, if not or unsure, halt and ask or confirm with the user.
|
||||
|
||||
3. **Checklist Processing**
|
||||
|
||||
If in interactive mode:
|
||||
|
||||
- Work through each section of the checklist one at a time
|
||||
- For each section:
|
||||
- Review all items in the section following instructions for that section embedded in the checklist
|
||||
@@ -316,7 +329,6 @@ If the user asks or does not specify a specific checklist, list the checklists a
|
||||
- Get user confirmation before proceeding to next section or if any thing major do we need to halt and take corrective action
|
||||
|
||||
If in YOLO mode:
|
||||
|
||||
- Process all sections at once
|
||||
- Create a comprehensive report of all findings
|
||||
- Present the complete analysis to the user
|
||||
@@ -324,7 +336,6 @@ If the user asks or does not specify a specific checklist, list the checklists a
|
||||
4. **Validation Approach**
|
||||
|
||||
For each checklist item:
|
||||
|
||||
- Read and understand the requirement
|
||||
- Look for evidence in the documentation that satisfies the requirement
|
||||
- Consider both explicit mentions and implicit coverage
|
||||
@@ -338,7 +349,6 @@ If the user asks or does not specify a specific checklist, list the checklists a
|
||||
5. **Section Analysis**
|
||||
|
||||
For each section:
|
||||
|
||||
- think step by step to calculate pass rate
|
||||
- Identify common themes in failed items
|
||||
- Provide specific recommendations for improvement
|
||||
@@ -348,7 +358,6 @@ If the user asks or does not specify a specific checklist, list the checklists a
|
||||
6. **Final Report**
|
||||
|
||||
Prepare a summary that includes:
|
||||
|
||||
- Overall checklist completion status
|
||||
- Pass rates by section
|
||||
- List of failed items with context
|
||||
@@ -592,21 +601,26 @@ sections:
|
||||
|
||||
==================== START: .bmad-creative-writing/checklists/beta-feedback-closure-checklist.md ====================
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 6. Beta‑Feedback Closure Checklist
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
---
|
||||
|
||||
checklist:
|
||||
id: beta-feedback-closure-checklist
|
||||
name: Beta‑Feedback Closure Checklist
|
||||
description: Ensure all beta reader notes are addressed or consciously deferred.
|
||||
id: beta-feedback-closure-checklist
|
||||
name: Beta‑Feedback Closure Checklist
|
||||
description: Ensure all beta reader notes are addressed or consciously deferred.
|
||||
items:
|
||||
- "[ ] Each beta note categorized (Fix/Ignore/Consider)"
|
||||
- "[ ] Fixes implemented in manuscript"
|
||||
- "[ ] ‘Ignore’ notes documented with rationale"
|
||||
- "[ ] ‘Consider’ notes scheduled for future pass"
|
||||
- "[ ] Beta readers acknowledged in back matter"
|
||||
- "[ ] Summary of changes logged in retro.md"
|
||||
...
|
||||
|
||||
- "[ ] Each beta note categorized (Fix/Ignore/Consider)"
|
||||
- "[ ] Fixes implemented in manuscript"
|
||||
- "[ ] ‘Ignore’ notes documented with rationale"
|
||||
- "[ ] ‘Consider’ notes scheduled for future pass"
|
||||
- "[ ] Beta readers acknowledged in back matter"
|
||||
- "[ ] Summary of changes logged in retro.md"
|
||||
...
|
||||
==================== END: .bmad-creative-writing/checklists/beta-feedback-closure-checklist.md ====================
|
||||
|
||||
==================== START: .bmad-creative-writing/data/bmad-kb.md ====================
|
||||
@@ -715,24 +729,28 @@ BMad Creative Writing transforms you into a "Creative Director" - orchestrating
|
||||
## Templates & Tools
|
||||
|
||||
### Character Development
|
||||
|
||||
- Comprehensive character profiles
|
||||
- Backstory builders
|
||||
- Voice and dialogue patterns
|
||||
- Relationship mapping
|
||||
|
||||
### Story Structure
|
||||
|
||||
- Three-act outlines
|
||||
- Save the Cat beat sheets
|
||||
- Hero's Journey mapping
|
||||
- Scene-by-scene breakdowns
|
||||
|
||||
### World Building
|
||||
|
||||
- Setting documentation
|
||||
- Magic/technology systems
|
||||
- Cultural development
|
||||
- Timeline tracking
|
||||
|
||||
### Publishing Support
|
||||
|
||||
- KDP formatting guidelines
|
||||
- Cover design briefs
|
||||
- Marketing copy templates
|
||||
@@ -741,6 +759,7 @@ BMad Creative Writing transforms you into a "Creative Director" - orchestrating
|
||||
## Genre Support
|
||||
|
||||
### Built-in Genre Checklists
|
||||
|
||||
- Fantasy & Sci-Fi
|
||||
- Romance & Thriller
|
||||
- Mystery & Horror
|
||||
@@ -748,6 +767,7 @@ BMad Creative Writing transforms you into a "Creative Director" - orchestrating
|
||||
- Young Adult
|
||||
|
||||
Each genre includes:
|
||||
|
||||
- Trope management
|
||||
- Reader expectations
|
||||
- Market positioning
|
||||
@@ -756,24 +776,28 @@ Each genre includes:
|
||||
## Best Practices
|
||||
|
||||
### Character Development
|
||||
|
||||
1. Start with internal conflict
|
||||
2. Build from wound/lie/want/need
|
||||
3. Create unique voice patterns
|
||||
4. Track arc progression
|
||||
|
||||
### Plot Construction
|
||||
|
||||
1. Begin with clear story question
|
||||
2. Escalate stakes progressively
|
||||
3. Plant setup/payoff pairs
|
||||
4. Balance pacing with character moments
|
||||
|
||||
### World Building
|
||||
|
||||
1. Maintain internal consistency
|
||||
2. Show through character experience
|
||||
3. Build only what serves story
|
||||
4. Track all established rules
|
||||
|
||||
### Revision Process
|
||||
|
||||
1. Complete draft before major edits
|
||||
2. Address structure before prose
|
||||
3. Read dialogue aloud
|
||||
@@ -813,11 +837,13 @@ Remember: BMad Creative Writing provides structure to liberate creativity, not c
|
||||
# Story Structure Patterns
|
||||
|
||||
## Three-Act Structure
|
||||
|
||||
- **Act 1 (25%)**: Setup, inciting incident
|
||||
- **Act 2 (50%)**: Confrontation, complications
|
||||
- **Act 3 (25%)**: Resolution
|
||||
|
||||
## Save the Cat Beats
|
||||
|
||||
1. Opening Image (0-1%)
|
||||
2. Setup (1-10%)
|
||||
3. Theme Stated (5%)
|
||||
@@ -833,7 +859,9 @@ Remember: BMad Creative Writing provides structure to liberate creativity, not c
|
||||
13. Break into Three (80%)
|
||||
14. Finale (80-99%)
|
||||
15. Final Image (99-100%)
|
||||
|
||||
## Hero's Journey
|
||||
|
||||
1. Ordinary World
|
||||
2. Call to Adventure
|
||||
3. Refusal of Call
|
||||
@@ -848,6 +876,7 @@ Remember: BMad Creative Writing provides structure to liberate creativity, not c
|
||||
12. Return with Elixir
|
||||
|
||||
## Seven-Point Structure
|
||||
|
||||
1. Hook
|
||||
2. Plot Turn 1
|
||||
3. Pinch Point 1
|
||||
@@ -857,6 +886,7 @@ Remember: BMad Creative Writing provides structure to liberate creativity, not c
|
||||
7. Resolution
|
||||
|
||||
## Freytag's Pyramid
|
||||
|
||||
1. Exposition
|
||||
2. Rising Action
|
||||
3. Climax
|
||||
@@ -864,6 +894,7 @@ Remember: BMad Creative Writing provides structure to liberate creativity, not c
|
||||
5. Denouement
|
||||
|
||||
## Kishōtenketsu (Japanese)
|
||||
|
||||
- **Ki**: Introduction
|
||||
- **Shō**: Development
|
||||
- **Ten**: Twist
|
||||
|
||||
Reference in New Issue
Block a user