Refocus discussion on open requirements and feature questions
Scanned 9/2/2026
Install to Claude Code
Skills Directorynpx -y skills add MarcusJellinghaus/mcp-workspace --skill issue_requirements --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Issue Requirements?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/marcusjellinghaus-issue-requirements)More formats (shields.io, HTML) on the badges page.
---
description: Refocus discussion on open requirements and feature questions
disable-model-invocation: true
---
# Issue Requirements
Refocus the conversation on open requirements after `/issue_analyse` has explored the issue and codebase.
## Instructions
Review the conversation so far and produce a structured summary:
1. **Decided items:** List what was already decided (from the issue's `## Decisions` section and the current conversation). Do not re-ask these.
2. **Questionable decisions:** If any existing decision seems risky or worth revisiting given what you've seen in the code, briefly note why. Don't block on it — just flag it.
3. **Open requirements / feature questions:** List only the remaining open questions that affect requirements or user-facing behavior. Implementation details are yours to decide — do not ask about them.
4. **Constraints & rationale identified:** List any non-obvious constraints or gotchas discovered during analysis (the "why" behind decisions, things downstream steps need to know).
**Suggested next step:** `/discuss` — to walk through the open questions one by one.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Use when a repo needs CodeGraph plus ast-grep for Codex MCP setup, exploration, impact analysis, structural search, or safe refactor planning.
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.
