القائمة
Suggests the next GitHub issue to work on from a PRD breakdown, confirms it with the user, and initiates the pre-implementation discussion.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Enforce the no-useEffect rule when writing or reviewing React code. ACTIVATE when writing React components, refactoring existing useEffect calls, reviewing PRs with useEffect, or when an agent adds useEffect "just in case." Provides the five replacement patterns and the useMountEffect escape hatch.
Break a PRD into independent GitHub issues, with backend-first then frontend-linked workflow. Each issue is fully discussed before implementation. Use when converting a PRD to actionable work items.
Implements a GitHub issue continuously until finished, documents the work and recommendations, commits, and closes the issue. Confirms the issue with the user only if it is not already in context.
Create a business-focused PRD through user interview, repo exploration, and rigorous clarification, then review it with the user before submitting it as a GitHub issue. Use when the user wants to write a PRD, create a product requirements document, scope a feature, or plan a new capability.
| name | start-next-issue |
| description | Suggests the next GitHub issue to work on from a PRD breakdown, confirms it with the user, and initiates the pre-implementation discussion. |
Select the next issue to work on from a PRD breakdown, confirm it with the user, and begin the discussion before implementation.
Present the suggested issue with:
Ask the user:
Wait for user confirmation before proceeding.
Once confirmed, start a structured pre-implementation discussion:
Interview the user relentlessly about every aspect of this plan until you reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one-by-one. For each question, provide your recommended answer. Ensure all points are clarified and the user approves the plan.
No coding begins until this step is fully completed and agreed upon.
