From thorough
Plans a specific feature or user story for implementation. Reads the project requirements document (REQUIREMENTS.md), identifies what needs to be built, clarifies any feature-specific details, and produces an implementation plan. Use after /thorough:sketch has created the requirements doc. Pass the feature name or user story as an argument.
How this skill is triggered — by the user, by Claude, or both
Slash command
/thorough:planThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Plan a specific feature for implementation, based on the project requirements.
Plan a specific feature for implementation, based on the project requirements.
Read REQUIREMENTS.md in the project root. If it doesn't exist, tell the user to run /thorough:sketch first.
Read the argument to understand which feature or user story to plan.
From the requirements doc, extract everything relevant to this feature:
Output a summary of what this feature involves.
If the requirements doc leaves any feature-specific details ambiguous, use AskUserQuestion to resolve them. Only ask about what's genuinely unclear for THIS feature — don't re-ask project-level decisions.
Search existing code for:
If this is a new project with no code yet, skip this step.
Produce a plan covering:
End with: "Ready to implement? Run /thorough:code to start."
If -f or --force is present: skip questions, produce the plan immediately with assumptions marked.
npx claudepluginhub yasinishyn/claude-thorough --plugin thoroughGenerates a detailed implementation plan for a feature, checking for duplicates against an existing feature index, identifying reusable components, and enforcing project conventions. Always pauses for human approval before execution.
Plans single features, endpoints, or infrastructure via Socratic conversation to uncover requirements, edge cases, failure modes, and constraints; outputs markdown feature plan artifact before coding.
Generates structured implementation plans for multi-step coding tasks from specs, breaking into TDD bite-sized steps with dependencies, files, tests, and commands before coding.