From groundwork
Clarifies feature requests via targeted questions on problems, users, outcomes, and detects contradictions in proposed requirements.
npx claudepluginhub etr/groundworkThis skill uses the workspace's default tool permissions.
Interactive workflow for clarifying feature requests and ensuring they don't conflict with existing requirements.
Provides Ktor server patterns for routing DSL, plugins (auth, CORS, serialization), Koin DI, WebSockets, services, and testApplication testing.
Conducts multi-source web research with firecrawl and exa MCPs: searches, scrapes pages, synthesizes cited reports. For deep dives, competitive analysis, tech evaluations, or due diligence.
Provides demand forecasting, safety stock optimization, replenishment planning, and promotional lift estimation for multi-location retailers managing 300-800 SKUs.
Interactive workflow for clarifying feature requests and ensuring they don't conflict with existing requirements.
Your current effort level is {{effort_level}}.
Skip this step silently if effort is high or higher AND you are Sonnet or Opus.
If effort is below high, you MUST show the recommendation prompt — regardless of model.
If you are not Sonnet or Opus, you MUST show the recommendation prompt - regardless of effort level.
Otherwise → use AskUserQuestion:
{
"questions": [{
"question": "Do you want to switch? Contradiction detection in feature requirements benefits from consistent reasoning.\n\nTo switch: cancel, run `/effort high` (and `/model sonnet` if on Haiku), then re-invoke this skill.",
"header": "Recommended: Sonnet or Opus at high effort",
"options": [
{ "label": "Continue" },
{ "label": "Cancel — I'll switch first" }
],
"multiSelect": false
}]
}
If the user selects "Cancel — I'll switch first": output the switching commands above and stop. Do not proceed with the skill.
When the user proposes a feature or change, ask clarifying questions to understand:
Core Questions (always ask):
Exploratory Questions (for open-ended or vague requests):
Conditional Questions (ask as relevant):
Keep questions focused - ask 2-3 at a time, not all at once. Build understanding iteratively.
Question Style:
Before proceeding with design, review for conflicts within the proposed feature:
If conflicts found, surface them and resolve before proceeding.