// Use when creating or updating a README. It enforces the 5-step 'Anti-Slop' pipeline and triggers the correct sub-skill for the current phase.
| name | grfp |
| description | Use when creating or updating a README. It enforces the 5-step 'Anti-Slop' pipeline and triggers the correct sub-skill for the current phase. |
Goal: Manage the lifecycle of README generation. Ensure no steps are skipped.
You MUST execute these phases in order. Do not skip to drafting until research is complete.
deep-dive (Get the Facts)crystal-ball (Get the Roadmap)brain-jam (Get the Voice)think-tank (Get the Patterns)pen-wielding (Write the Artifact)Before acting, checks the current context to decide which skill to trigger.
Condition: If you do not have a "Reality Report" (from Deep Dive) in the chat history...
Action: Invoke deep-dive immediately.
Do not ask: "Shall we start?" Just start.
Condition: If you have the Reality Report, but lack a "Roadmap & Future Improvements" table...
Action: Invoke crystal-ball immediately.
Condition: If you have Facts + Roadmap, but have not agreed on an "Angle" (Deep Tech vs. Pragmatist)...
Action: Invoke brain-jam immediately.
Condition: If you have the Angle, but lack a "Research Results" audit of similar repos...
Action: Invoke think-tank immediately.
Condition: If you have Facts + Roadmap + Angle + Patterns...
Action: Invoke pen-wielding to generate the final artifact.
When a sub-skill completes (e.g., deep-dive finishes), do not stop.
Example: "Deep Dive is complete. I see the Reality Report. Moving to Phase 2: Invoking crystal-ball..."
Use when determining project tone, voice, and marketing angle after deep-dive and crystal-ball phases. Conducts brainstorming session with Gemini.
Use when analysing future opportunities after deep-dive phase. Identifies performance improvements, technical debt, security hardening, and feature gaps. Outputs roadmap candidates table.
Use when starting the README pipeline to extract technical facts from codebase. Identifies project type, tech stack, dependencies, entry points, CI configuration. Outputs Reality Report.
Use when writing the final README after all phases complete. Synthesises outputs from deep-dive, crystal-ball, brain-jam, and think-tank. Applies Anti-Slop style guide.
Use when researching documentation patterns after brain-jam phase. Analyses exemplar READMEs from similar high-star repositories, scores against rubric, extracts patterns.