SuperAPI AI Directory
Partner with us中文AI newsFavorites
Skillsbro-give-me-plan

bro-give-me-plan

Agents & models

View repository

Updated 10-15 19:47

About this skill

Bro Give Me Plan

Your task is to create an implementation plan for a specific task and problem. DO NOT WRITE the code itself, only create the plan. If the person needs a specification of the result without implementation steps, STOP and suggest /bro-give-me-spec.

GENERAL RULES

  • MUST follow dialogue rules!
  • MUST follow implementation hygiene!
  • MUST follow and NOT violate work order!
  • The plan MUST be unambiguous, with no variations or questions in it. All questions and variations MUST be resolved with the person.
  • The plan MUST NOT substitute implementation steps with code, diff, patches, or pseudocode.
  • If the plan has an acceptance criteria section, they MUST cover the target result with observable statements. Do NOT specify the verification method (automated test, manual check, build, etc.) in the criterion.

CONSTRAINTS / STOP

  • FORBIDDEN to violate the work order and workflow rules
  • FORBIDDEN to invent or make up facts or hypotheses. Any ambiguity MUST be resolved before proceeding to create the plan.
  • FORBIDDEN when CreatePlan is available inline / file (or an analogue), to ask for a choice of

WORK ORDER

  1. GATHER information for creating an unambiguous plan: code, context:
    • Do not ask what can be established with high confidence.
    • Mark what is inferred as inferred until the user confirms it.
  2. REQUEST the missing information from the person. MUST follow the dialogue rules.
  3. DETERMINE which workflow needs to be used, following the workflow determination rules.
  4. CONNECT the file with the instructions of the selected workflow. FOLLOW all instructions from the selected workflow.

WORKFLOW DETERMINATION RULES

Below are the rules describing how to determine which workflow to use depending on the request. DO NOT READ the file with instructions inline / file until you confirm the choice with the person. For create-plan confirmation is not needed — connect immediately after selection. FIRST evaluate the task by the following criteria:

  • whether the tool is available in the session CreatePlan (or an analogous harness for creating a plan);
  • whether a separate file artifact of the plan is needed (new chat, review outside the chat, explicit "Scope" / "Acceptance criteria");
  • whether the steps in the chat are sufficient without a separate file.

SELECT a workflow based on the criteria obtained earlier. For inline и file — STOP и REQUEST confirmation of the selected workflow from the user. SAY why exactly this workflow you recommend. For create-plan confirmation DO NOT request.

create-plan

Use if:

  • the tool is available in the current session CreatePlan (or an analogous harness for creating a plan)

When selecting this workflow DO NOT ASK inline / file и DO NOT REQUEST confirmation.

File with instructions: create-plan

inline

Use if:

  • CreatePlan (or an analogue) is unavailable
  • a small task and a clear target result
  • the scope and verification fit into the steps and/or are already clear from the context
  • no artifacts are needed before and after implementation

File with instructions: inline-plan

file

Use if:

  • CreatePlan (or an analogue) is unavailable
  • a small task and a clear target outcome
  • the plan must survive a new chat, a file artifact is needed
  • explicit sections "Scope" or "Acceptance criteria" are needed separately from the steps

File with instructions: file-plan

Large multi-stage initiatives DO NOT plan through this skill as one big plan: first lock in the desired outcome via /bro-give-me-spec, and make plans for specific small tasks.