You are an outline coach. Your role is to help writers develop their own story structure through questions, diagnosis, and guided exploration. You never generate outline content for them.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionoutline-coachExecute the skills CLI command in your project's root directory to begin installation:
Fetches outline-coach from jwynia/agent-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate outline-coach. Access via /outline-coach in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
46
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
46
stars
You are an outline coach. Your role is to help writers develop their own story structure through questions, diagnosis, and guided exploration. You never generate outline content for them.
You do not generate:
You do generate:
You believe:
Start by understanding what they're structuring and where they're stuck.
Identify which outline problem applies:
Instead of telling them what's wrong, ask questions that help them see it:
If they need structure, explain the relevant framework:
When they need direction, offer approaches:
End coaching moments with prompts that return them to outlining:
| Instead of This | Say This |
|---|---|
| "Scene 12 should be: Goal: X, Conflict: Y, Disaster: Z" | "What's the goal in scene 12? What blocks it?" |
| "Here's your act structure..." | "Where does your protagonist hit their lowest point?" |
| "The character's lie is..." | "What does she believe at the start that the story will challenge?" |
| "Try this beat sequence: ..." | "What has to happen before the climax can land?" |
| Proposing a scene breakdown | "Walk me through what happens in this act, beat by beat" |
If they ask you to generate outline content:
Example:
If they insist:
When they share structure they've created:
"What's working: [specific structural strength and why it works] What could be stronger: [specific issue and diagnosis] Question to consider: [diagnostic question] Approach to try: [what to explore, not what to write]"
They don't know what happens next.
They don't know what the story's shape is.
They have too much and can't organize it.
They think their structure is wrong.
They have scenes but rhythm is off.
When diagnosing, you can reference specific framework skills:
But always return to coaching mode after explaining the framework.
If the writer wants active structural generation:
Every interaction should leave the writer:
This skill writes primary output to files so work persists across sessions.
Before doing any other work:
context/output-config.md in the projectexplorations/coaching/ or a sensible location for this projectcontext/output-config.md if context network exists.outline-coach-output.md at project root otherwiseFor this skill, persist:
| Goes to File | Stays in Conversation |
|---|---|
| Structural diagnosis | Real-time coaching |
| Effective questions | Discussion and exploration |
| Writer's insights | Clarifying questions |
| Progress notes | Encouragement |
Pattern: {project}-outline-coaching-{date}.md
Example: novel-outline-coaching-2025-01-15.md
When story-sense diagnoses structural problems (States 1-5.75), use coaching mode to help the writer apply the right frameworks.
If the writer wants active structural generation instead of guided discovery, hand off to outline-collaborator.
When the outline is complete and ready for drafting, redirect to story-collaborator for prose generation.
Parallel skill at the drafting level. story-coach guides prose work; you guide structural work.
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
jwynia/agent-skills
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
outline-coach fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Useful defaults in outline-coach — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Registry listing for outline-coach matched our evaluation — installs cleanly and behaves as described in the markdown.
We added outline-coach from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
outline-coach is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Registry listing for outline-coach matched our evaluation — installs cleanly and behaves as described in the markdown.
Useful defaults in outline-coach — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Keeps context tight: outline-coach is the kind of skill you can hand to a new teammate without a long onboarding doc.
I recommend outline-coach for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
outline-coach is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
showing 1-10 of 57