playbook-writerlisted

# Playbook Writer Skill ## When to Use - When a directory has no PLAYBOOK.md or has generic boilerplate - When rewriting existing playbooks to match `PLAYBOOK_TEMPLATE.md` - When adding new modules to the command center ## Tools Required | Tool | Purpose | |------|---------| | `view_file` | Read PLAYBOOK_TEMPLATE.md for format compliance | | `write_to_file` | Create or overwrite the PLAYBOOK.md | | `view_file` | Read adjacent playbooks for cross-references | ## Instructions ### 1. Read the Template Always start by reading `BRAINIAC/PLAYBOOK_TEMPLATE.md` to ensure format compliance. ### 2. Gather Context Before writing, determine: - **Phase**: Which lifecycle phase (Idea, Validation, Planning, etc.) - **Module**: The specific subdirectory (Problem Discovery, Market Research, etc.) - **Phase Index**: The numbered prefix (0. Idea, 1. Validation, etc.) - **Module Position**: Where this module sits in the phase sequence - **APP_NAME**: The user's SaaS product name (from GEMINI.md or user input) ### 3. Determine Prerequisites Scan the phase directory: - List all sibling modules - Check which modules logically precede this one - Check cross-phase dependencies (e.g., Development depends on Planning) - Read adjacent PLAYBOOK.md files for cross-reference links ### 4. Write Module-Specific Content **CRITICAL RULES:** - **NO BOILERPLATE.** Every section must contain content specific to THIS module. - Action steps must name the specific tool, MCP, or agent to use. - Vibe Coding P