stark-ai-de/agent-skills / skills/cursor-operations/cursor-spec-interviewer
cursor-spec-interviewer
VerifiedTurn ambiguous coding requests into verified Cursor Agent implementation specs. Use when the user wants requirements, an implementation plan, or a spec before coding; include source checks, needed ADRs, and agreed delivery. Do not use for already specified direct implementation or memory cleanup.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 7.8 KB |
| assets/cursor-execution-prompt.md | markdown | 6.1 KB |
| assets/example-repo-refactor.spec.md | markdown | 10.0 KB |
| assets/example-small-task.spec.md | markdown | 3.5 KB |
| assets/spec-template.compact.md | markdown | 1.5 KB |
| assets/spec-template.deep.md | markdown | 3.9 KB |
| assets/spec-template.standard.md | markdown | 3.3 KB |
| references/adr-gate.md | markdown | 2.7 KB |
| references/artifact-destinations.md | markdown | 3.0 KB |
| references/host-adapters.md | markdown | 5.5 KB |
| references/question-bank.md | markdown | 4.8 KB |
| references/rollout-checklist.md | markdown | 2.7 KB |
| references/source-challenge.md | markdown | 2.6 KB |
| references/spec-rubric.md | markdown | 6.5 KB |
| references/workflow-details.md | markdown | 9.0 KB |
references/rollout-checklist.md
View on GitHub# Rollout Checklist
Use this reference when writing the validation, rollout, and rollback sections of a spec.
## Validation Plan
- List the repo's real lint, typecheck, unit, integration, e2e, and build commands; mark missing ones `unspecified` instead of inventing them.
- Include at least one concrete manual verification scenario per user-visible behavior change.
- For migrations or refactors, include a search or count check that proves the old pattern is gone or bounded.
- Name the review focus areas: regression hotspots, security-sensitive paths, and contract or schema changes.
## Phased Rollout
Phase the work when any of these apply: repo-wide scope, shared contracts, data migrations, auth/billing surfaces, or diffs too large to review safely in one pass.
For each phase, the spec should state:
- the bounded work items in the phase,
- a validation gate that must pass before the next phase starts,
- whether the phase is independently shippable or must land with others.
## Migration and Compatibility
- State whether data migration, backfill, config changes, or feature flags are required.
- State backward-compatibility expectations and any deprecation window.
- Keep a temporary compatibility shim only with an explicit removal condition.
## Rollback
- Define the rollback trigger: which failures or metrics justify reverting.
- Define the rollback procedure: what gets reverted, what can safely stay.
- Call out one-way doors such as destructive migrations or deleted contracts, and require explicit user confirmation for them.
## Monitoring
- Name what to watch during rollout: error rates, latency, auth failures, job backlogs, or the repo's existing dashboards.
- For repos without monitoring, fall back to log checks and manual verification steps and say so in the spec.
## Spec Risk Checklist
| Risk / edge case | Recommended mitigation |
| -------------------------------- | --------------------------------------------------------------------------- |
| Hidden migrations / rollout risk | force rollout and rollback notes for standard and deep modes |
| Shared-contract breakage | list affected consumers and gate the phase on contract tests |
| Auth, billing, or secret paths | call out explicitly, require manual verification, avoid speculative edits |
| Too-large diffs | phase the work by package or module with validation gates |
| Partial cutover confusion | document the default path and add a guard against reintroducing the old one |
| Silent behavior drift | pin user-visible behavior in acceptance criteria and manual checks |
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |