break-req
Break Req
This skill is requirements-only.
Hard Stop
Never implement code, edit product files, create issues, publish to GitHub, run create-git-issue, run run-with-it, spawn implementation agents, or invoke external coding agents.
The only file this skill may create or update is technical_requirements.md.
Interrogate me relentlessly about every aspect of this requirement (both functional and non functional) until we have a complete technical picture. Walk down each branch of the decision tree, resolving blockers and dependencies one at a time. For each question, provide your recommended answer.
Ask the questions one at a time.
If a question can be answered by exploring the codebase, explore the codebase instead of asking.
Cover all relevant layers as you go:
- UI: frameworks, third-party libraries, component state management.
- Backend: packages, API contracts, service architecture.
- Data: schemas, migrations, contracts between layers.
Once all branches are resolved:
- Compile every decision and resolution into
technical_requirements.md. - Stop.
- Inform the user that requirements are ready and they can now run the
create-git-issueskill.
Do not proceed beyond technical_requirements.md, even if the next step is obvious.
More from chanakya-net/ai-skills
save-tokens
>
24create-git-issue
Create a PRD from current context, then break it into tracer-bullet issues and publish everything to the project issue tracker. Use when user wants end-to-end issue creation from a plan, idea, or requirement.
21tdd-implementation
Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, asks for test-first development, or wants stronger integration tests.
21run-with-it
Route issue-running automation through a deterministic control plane that selects agent + model from registry, can coordinate multiple safe parallel agents, and executes the unified run-agent runner.
20