From devflow
Frames a problem or opportunity into a structured problem statement with clear scope boundaries. Searches for prior art and checks feasibility before investing in full requirements. This is the first step in the upstream SDLC workflow, before creating a PRD.
npx claudepluginhub joshuarweaver/cascade-code-general-misc-4 --plugin codingthefuturewithai-claude-code-primitivesThis skill is limited to using the following tools:
**Say exactly:** "SKILL INVOKED: pm/discover"
Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.
Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.
Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.
Say exactly: "SKILL INVOKED: pm/discover"
You are helping the user frame a problem or opportunity and produce a structured problem statement with clear scope boundaries.
Accept rough ideas in any form — unstructured text, existing documents, URLs, pasted fragments — and help transform them into a well-structured problem statement. Search for prior art across all configured backends to avoid reinventing the wheel. Help set clear scope boundaries.
Load configuration: Read ~/.claude/plugins/config/devflow/config.md to know what backends are available. Check .devflow/project.md for existing upstream context.
Accept input in any form: The user may bring a vague idea, existing documents, or a well-formed problem. Auto-detect what you're working with and adapt:
Search for prior art: Before investing in framing, use the prior-art-search agent to search ALL configured backends in parallel — doc backends, issue tracker, and codebase. This is heavy read work that would pollute the main conversation context, so it MUST run as a subagent. The agent returns a structured summary: what was found, where, and how it relates. Surface the results to the user.
Frame the problem: Use references/problem-statement-template.md to guide the conversation. Assess coverage against the template, identify gaps, help fill them through conversation.
Store the result: Present storage options (configured backends + local .devflow/). Let the user choose. Update .devflow/project.md with the artifact location.
.devflow/ is always an option.This skill produces a PROBLEM STATEMENT only. NO technical decisions.
✅ IN SCOPE (problem framing):
❌ OUT OF SCOPE (belongs in downstream skills):
pm/define-architecturepm/define-architecturepm/define-architecturepm/define-architecturepm/define-prdIf the user mentions technical choices (e.g., "we'll use Laravel"), capture them as context/constraints in the problem statement, but do NOT make those decisions here. The architecture skill will formalize them later.
Skill complete.