القائمة
Use when a Jumbo goal fails QA review and needs to be returned for rework. Records review issues and routes the goal back to the implementing agent with actionable feedback.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when the user's prompt is delivered outside the execution context of an existing Jumbo goal, the prompt is imbued with an objective that is not already defined as a Jumbo goal.
Use when a Jumbo-managed agent file tells the agent to bootstrap the session. Runs Jumbo's session router only when the agent has not already received a routed Jumbo command.
Use when an agent needs to discover Jumbo command syntax after session routing. Directs command discovery through CLI help instead of static command catalogs.
Use when implementation discovers durable project context that must be recorded in Jumbo. Captures decisions, components, dependencies, relations, guidelines, and invariants during the work.
Use when the user corrects an approach, constraint, workflow, or style. Converts corrections into Jumbo guidelines or invariants so future sessions receive the constraint.
Use when a Jumbo goal has been approved by QA review and needs architectural reconciliation before closing. Captures new learnings, updates stale entities, and ensures documentation reflects the work performed.
| name | reject-jumbo-goal |
| description | Use when a Jumbo goal fails QA review and needs to be returned for rework. Records review issues and routes the goal back to the implementing agent with actionable feedback. |
Prompt: Reject a Jumbo goal that failed QA review, recording the specific issues found so the implementing agent can address them and restart.
When a goal is rejected, the implementing agent receives the review issues as its primary guidance for rework. Vague or incomplete rejection feedback causes wasted rework cycles — the agent guesses at what's wrong, fixes the wrong things, and resubmits with the same issues. Precise, actionable rejection feedback is the fastest path to a passing review.
Before rejecting, ensure you have a clear, specific list of every issue found during QA review. Each issue must be:
jumbo goal reject --id <goal-id> --issues "<detailed review issues>"
The rejection output confirms:
After rejection, the implementing agent should:
jumbo goal start --id <goal-id>
jumbo goal submit --id <goal-id>
If a next goal is queued, its ID will be displayed for reference, but the rejected goal takes priority.