القائمة
Verify all issues related to the current PRD have been completed and then delete all issues and the PRD itself to maintain a clean project management environment.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | clean-up-prd |
| description | Verify all issues related to the current PRD have been completed and then delete all issues and the PRD itself to maintain a clean project management environment. |
Review the current PRD and all associated issues. Verify that all tasks related to the PRD have been completed successfully. If any issues are still open, provide a summary of the remaining tasks and ask the user if they would like to proceed with cleaning up the PRD or if they want to address the remaining issues first.
Assuming all issues are completed, proceed to delete all issues associated with the PRD. After confirming that all issues have been removed, delete the PRD itself.
Always wait for my approval before deleting any issues or the PRD.
After deleting the PRD and issues commit the changes to the repository with a clear commit message indicating that the PRD and associated issues have been cleaned up and the feature has been completed.
Fully implement a PRD's issues end-to-end — a parallel read-only investigation pass, then strictly serial TDD implementation on the PRD's shared feature branch, HITL issues left for a human. Use after write-a-prd + prd-to-issues, when the user wants to "implement the PRD", run the whole issue queue, or run /implementation.
Check NuGet analyzer packages for newer versions and, if any are found, autonomously drive the entire release end-to-end — PRD and issues, /implementation, cleanup, changelog, PR with auto-merge, tag, and a published NuGet release. Use when the user wants to bump analyzer dependencies or asks "are there any NuGet updates?".
Pick the next AFK issue from issues/ and implement it end-to-end via TDD, then commit. Use when the user wants to advance the ralph queue, asks to "work on the next issue", or runs this in a /loop.
Implement a specific piece of work described in the skill argument, end-to-end via TDD, then commit. Use when the user wants to work on a described task rather than picking from the issue queue.
Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.
Triggered when the user is skeptical or suspicious of a previous response. The
