Creation quality field guide
Plant better instructions.
Harvest stronger work.
Spores turns quality habits into practical role arrangements. Use the guidance as a starting structure, then change every role, support role, model, and route to fit the project.
Quality multipliers
Small controls.
Compounding results.
01Define the finish line
State the intended audience, usable deliverable, constraints, and proof of completion before assigning any box.
02Separate creation from verification
Give drafting and fact-checking to different boxes so the model that made a claim is not its only reviewer.
03Use support roles deliberately
A primary Writer with a fact-checker behaves differently from a Writer with an editor. Choose the secondary responsibility that protects the weakest part of the task.
04Route evidence with the work
Every handoff should include sources, assumptions, unresolved risks, and the exact decision the next box must make.
05Keep one authority source
Name the controlling brief, canon, specification, or dataset. Tell every role what wins when materials conflict.
06Match response guidance to consequence
Use light guidance for variations, medium for production drafting, and heavy for architecture, verification, security, or irreversible decisions. This setting is passed as instruction text; it does not guarantee a provider-specific reasoning mode.
07Ask for visible checks
Require acceptance criteria, edge cases, contradictions, and a concise verification record instead of an unsupported claim that work is complete.
08Revise the route, not only the prompt
If results drift, change which role receives the work, what evidence travels with it, and what the supervisor must flag during its post-output review.
Suggested configurations
Start with a role chain.
Then make it yours.
These are suggestions, not locked presets. The Workbench keeps every functional assignment editable.
PROJECT CATEGORYFiction + worldbuilding
- Suggested primary chain
- Planner → Researcher → Writer → Critic → Reviewer → Verifier
- Useful support roles
- context-keeper, researcher-aide, editor, devils-advocate
- Quality focus
- Preserve canon, character causality, voice, and continuity before polishing prose.
PROJECT CATEGORYManuscript editing
- Suggested primary chain
- Planner → Critic → Writer → Reviewer → Verifier → Summarizer
- Useful support roles
- editor, context-keeper, fact-checker, formatter
- Quality focus
- Separate developmental, line, continuity, and final-proof passes.
PROJECT CATEGORYWebsite or application
- Suggested primary chain
- Planner → Researcher → Coder → Critic → Reviewer → Verifier
- Useful support roles
- researcher-aide, tester, devils-advocate, formatter
- Quality focus
- Lock scope and acceptance criteria before implementation; verify behavior, accessibility, and failure states.
PROJECT CATEGORYGame system
- Suggested primary chain
- Planner → Researcher → Coder → Critic → Verifier → Reviewer
- Useful support roles
- context-keeper, tester, devils-advocate, note-taker
- Quality focus
- Track rules interactions, progression, exploits, player feedback, and implementation constraints.
PROJECT CATEGORYResearch report
- Suggested primary chain
- Planner → Researcher → Critic → Writer → Verifier → Summarizer
- Useful support roles
- researcher-aide, fact-checker, devils-advocate, formatter
- Quality focus
- Separate evidence collection, claim testing, synthesis, and citation verification.
PROJECT CATEGORYCurriculum + assessment
- Suggested primary chain
- Planner → Researcher → Writer → Critic → Verifier → Reviewer
- Useful support roles
- researcher-aide, editor, tester, formatter
- Quality focus
- Align objectives, instruction, practice, accessibility, and assessment evidence.
PROJECT CATEGORYImage campaign
- Suggested primary chain
- Planner → Researcher → Writer → Critic → Reviewer → Verifier
- Useful support roles
- context-keeper, researcher-aide, editor, tester
- Quality focus
- Protect visual authority, subject identity, composition variety, and delivery specifications.
PROJECT CATEGORYVideo production
- Suggested primary chain
- Planner → Writer → Voice → Critic → Reviewer → Verifier
- Useful support roles
- context-keeper, editor, fact-checker, formatter
- Quality focus
- Coordinate story beats, shot logic, spoken timing, continuity, and technical delivery.
PROJECT CATEGORY3D asset pipeline
- Suggested primary chain
- Planner → Researcher → Coder → Critic → Verifier → Reviewer
- Useful support roles
- researcher-aide, tester, context-keeper, formatter
- Quality focus
- Carry scale, topology, materials, rigging, format, and engine constraints through every handoff.
PROJECT CATEGORYData analysis
- Suggested primary chain
- Planner → Researcher → Coder → Critic → Verifier → Summarizer
- Useful support roles
- fact-checker, tester, devils-advocate, formatter
- Quality focus
- Protect data provenance, assumptions, reproducibility, uncertainty, and interpretation.
PROJECT CATEGORYSecurity review
- Suggested primary chain
- Planner → Researcher → Coder → Critic → Verifier → Reviewer
- Useful support roles
- devils-advocate, tester, fact-checker, note-taker
- Quality focus
- Separate discovery, exploitability analysis, validation, remediation, and regression checks.
PROJECT CATEGORYProduct launch
- Suggested primary chain
- Planner → Researcher → Writer → Critic → Voice → Verifier
- Useful support roles
- researcher-aide, fact-checker, editor, context-keeper
- Quality focus
- Keep audience, claims, positioning, channel format, and launch evidence consistent.