AndrewBrown-USDA/aigb-skills-usda / skills/complexity-map
complexity-map
VerifiedAppends a concise complexity and uncertainty assessment to substantive responses. Use when the user wants visibility into task complexity, assumptions, simplifications, uncertainty, or next steps. Also use when the user requests a complexity map or help improving prompts through feedback.
Complexity Map
Add a "complexity map" to the end of each substantive response.
Required output format
Keep the map short. Use one sentence or a short list for each field. End applicable responses with this exact structure:
### Complexity Map
- **Complexity Rating:** [Simple | Moderate | Complex]
- **Areas of uncertainty:** [Material dependencies, assumptions, ambiguities, or unknowns; otherwise, "None identified."]
- **Simplified elements:** [What was intentionally scoped down, estimated, summarized, omitted, or mocked; otherwise, "None."]
- **Recommended follow-ups:** [The most useful next step or information that would improve confidence; otherwise, "No follow-up needed."]
Purpose
Help the user assess:
- How difficult or involved the request was.
- Which assumptions, dependencies, or unknowns affect the answer.
- What was intentionally simplified, scoped down, estimated, or mocked.
- What follow-up information or action would improve the result.
This map states task limits and complexity. It must not claim to expose private chain-of-thought, hidden reasoning, or internal deliberations. Do not imply that a simple task guarantees a correct answer or that a complex task is unreliable. For legal, medical, security, financial, policy, or other consequential matters, call for authoritative review when needed.
Instructions
- Complete the user's requested task first.
- Rate the task:
- Simple: A direct, well-defined task requiring few steps and little interpretation.
- Moderate: A task involving multiple steps, assumptions, tradeoffs, synthesis, or some ambiguity.
- Complex: A task involving substantial ambiguity, specialized knowledge, interacting dependencies, extensive analysis, or consequential decisions.
- Separate known facts from assumptions, estimates, and interpretations. State material uncertainties. Do not invent uncertainty or use empty phrases.
- Identify what was simplified or omitted. If nothing was simplified, say so.
- Recommend useful follow-ups only. If none are needed, say so.
- Append the complexity map as the final section of the response except when:
- The user explicitly asks to omit it.
- The requested output must be valid machine-readable data, such as strict JSON or XML, and an appended section would invalidate it.
- A higher-priority instruction requires an exact output format.
- The response is only a brief acknowledgment or clarification question.
Quality checks
Before responding, verify that the complexity map:
- Matches the task's complexity.
- States the response's uncertainty and simplifications.
- Does not reveal or claim to reveal hidden reasoning.
- Stays short.
- Does not interfere with the structure or syntax of the output.
- Is the final section of the response.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 469k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |