P7 — COMPREHENSIVE Protocol
Full analytical treatment for major work or archival purposes.
Configuration
yaml
ROLES_ACTIVE: PRIMARY: [ALL NINE ROLES] SECONDARY: [] INACTIVE: [] DOCUMENTS: GENERATE: [ALL EIGHT CORE DOCUMENTS + SUPPLEMENTS AS WARRANTED] EXCLUDE: [] DEPTH: Maximum INGESTION: Four-phase protocol
This Protocol = Full SKILL.md Activation
P7 activates the complete script-analysis-dramaturgical skill. See /mnt/project/SKILL.md for full specification.
Analyst Role Matrix
All nine perspectives active:
| Role | Focus | Minimum Observations |
|---|---|---|
| AESTHETE | Form, beauty, style | 3 |
| DRAMATURGIST | Structure, rhythm, tension | 5 |
| NARRATOLOGIST | Mechanism, theory application | Framework complete |
| ART_HIST | Historical, intertextual context | As relevant |
| CINEPHILE | Comparable works | 3 |
| RHETORICIAN | Language, argument, dialogue | Assessment complete |
| PRODUCER | Practical considerations | If requested |
| ACADEMIC | Theoretical rigor | Maintained throughout |
| FIRST-READER | Engagement response | Honest assessment |
Four-Phase Ingestion
code
PHASE 1: INITIAL READ ├── Read script completely without annotation ├── Note immediate emotional/engagement responses └── Capture [FIRST-READER] reactions PHASE 2: STRUCTURAL READ ├── Identify act breaks (even if unconventional) ├── Mark turning points and structural nodes └── Note temporal structure and time span PHASE 3: ANALYTICAL READ ├── Annotate scene-by-scene ├── Tag every beat with function └── Map character arcs and transformations PHASE 4: SYNTHESIS ├── Cross-reference observations ├── Identify patterns across readings └── Formulate diagnostic assessments
Eight Core Documents
| # | Document | Purpose |
|---|---|---|
| 1 | Coverage Report | Executive summary + recommendation |
| 2 | Beat Map | Exhaustive scene-by-scene mapping |
| 3 | Structural Analysis | Act/movement architecture |
| 4 | Character Atlas | All characters + arcs |
| 5 | Thematic Architecture | Theme layers + motif tracking |
| 6 | Diagnostic Report | Structural problems + solutions |
| 7 | Theoretical Correspondence | Framework mapping |
| 8 | Revision Roadmap | Prioritized action items |
Optional Supplements
Generate as warranted by work:
| Supplement | When to Include |
|---|---|
| Production Notes | Budget/casting/feasibility relevant |
| Comparative Analysis | Genre positioning important |
| Dialogue Analysis | Language patterns notable |
| Visual Grammar | Camera/staging/spectacle significant |
| Market Positioning | Commercial assessment requested |
Framework Application (Full)
Apply all established algorithms:
| Algorithm | Tests |
|---|---|
| McKee | Gap analysis, progressive complications, controlling idea |
| Aristotle | Unity, catharsis, recognition, reversal |
| South Park | But/Therefore causal binding |
| Phoebe Waller-Bridge | Three-obstacle layering per scene |
| Larry David | Cascading consequences |
| Bharata Muni | Rasa identification, bhava mapping |
| Kubrick | Non-submersible units present? |
| Attention Mechanics | Mode consistency, engagement diagnosis |
Quality Checklist
Before delivery:
code
â–¡ Every scene/beat is mapped (no gaps) â–¡ All named characters are profiled â–¡ All turning points are identified â–¡ Diagnostic questions are answered with evidence â–¡ Issues include specific line/page references â–¡ Revision items include actionable suggestions â–¡ ASCII diagrams render correctly â–¡ All nine roles have contributed observations â–¡ All relevant frameworks applied â–¡ Cross-references to comparable works included
Template References
- •
/mnt/project/coverage-template.md - •
/mnt/project/beat-map-template.md - •
/mnt/project/structural-template.md - •
/mnt/project/character-template.md - •
/mnt/project/diagnostic-template.md
Delivery Format
All documents delivered as markdown with:
- •ASCII diagrams for visual structures
- •Tables for data-dense sections
- •Code blocks for formulas and tests
- •Consistent heading hierarchy
- •Role-tagged observations throughout