Requirements Interview
Interview before PRD or spec work by exploring code first, resolving product and technical ambiguity, and deciding the right artifact. Use when: starting a feature, expanding features, clarifying requirements. Do not use: for spec-only work, requirements already clear.
Install
$ agentstack add skill-woliveiras-geremmyas-requirements-interview ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-woliveiras-geremmyas-requirements-interview) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Requirements Interview
Reach shared understanding before writing PRDs, specs, plans, or tasks.
Process
- Commit permission (first): Before other questions, ask: "Do I have
permission to create git commits for this work, or do you handle commits yourself?" Record the answer for the session. If the user does not grant permission, downstream skills must not run git-commit; report changed files instead.
- Explore the relevant code, docs, specs, PRDs,
GLOSSARY.md,CONTEXT.md,
and ADRs before asking questions.
- Classify the work:
- new feature
- existing feature expansion
- bugfix
- refactor
- documentation/setup
- For existing features, decide whether the product flow changes. If it does,
update the PRD before writing specs. If it does not, write targeted specs. If a PRD exists without a spec, do not proceed to implementation until a spec is written from the PRD.
- Ask one question at a time. For each question, include a recommended answer
based on the codebase and documents.
- Challenge vague or overloaded terms and propose canonical vocabulary.
- Record resolved decisions in the right artifact: PRD, spec, ADR, or
tasks.md.
Rules
- Do not skip the commit permission question at the start.
- Do not ask questions that code or existing docs can answer.
- Do not write a spec until the key branches of the decision tree are resolved.
- Do not create an ADR unless the decision is complex, hard to reverse,
surprising without context, and based on a real trade-off.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: woliveiras
- Source: woliveiras/geremmyas
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.