From spec-creator
Extend an existing project specification by identifying gaps and interviewing the user to fill them. Use when the user says "update the spec", "add to the spec", "the spec is missing X", or wants to expand requirements, design decisions, or operational details in an existing spec file.
npx claudepluginhub thejavaguy/tjg-claude-marketplace --plugin spec-creatorThis skill is limited to using the following tools:
Extend an existing project specification at $ARGUMENTS by identifying what is underspecified, interviewing the user to fill the gaps, and merging the new content back in.
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Analyzes competition with Porter's Five Forces, Blue Ocean Strategy, and positioning maps to identify differentiation opportunities and market positioning for startups and pitches.
Extend an existing project specification at $ARGUMENTS by identifying what is underspecified, interviewing the user to fill the gaps, and merging the new content back in.
Step 1 — Validate and read the spec.
Check that $ARGUMENTS exists and is non-empty. If the file is missing or empty, use AskUserQuestion to ask the user to confirm the path or provide the content before proceeding.
Read the file and output a brief, structured summary:
Do not ask questions yet.
Step 2 — Identify gaps.
Audit the spec against the following gap categories. For each category, note whether it is fully covered, partially covered, or absent:
| Category | Examples of what to look for |
|---|---|
| Functional requirements | User stories, edge cases, error flows, permissions |
| Non-functional requirements | Performance targets, SLAs, scalability, accessibility |
| Data model | Entities, relationships, constraints, migration strategy |
| API / integration | Endpoints, contracts, third-party services, auth flows |
| Security | Threat model, input validation, secrets management |
| Deployment / ops | Environments, CI/CD, rollback, monitoring, alerting |
| Testing strategy | Unit, integration, e2e, load testing expectations |
| Open questions | Unresolved trade-offs, deferred decisions |
Prioritise gaps that would block implementation or cause rework. Ignore cosmetic or editorial gaps.
Step 3 — Interview.
For each prioritised gap, use AskUserQuestion to ask one focused question at a time. Rules:
Example question shapes:
Step 4 — Update the spec.
Merge answers into $ARGUMENTS:
After writing, re-read the updated file and verify:
Use AskUserQuestion to show the user a one-line summary of what was added and ask if the result looks correct. If they request changes, apply them before closing.