$npx -y skills add human-avatar/skills-for-humanity --skill s4h-constraint-rule-inversionFlips a constraint into a creative driver — uses the limit as the generative force rather than working around it. Triggers: 'invert the constraint', 'use the limitation', 'constraint as feature', 'what if this limit was the requirement'.
| 1 | # Constraint Rule Inversion |
| 2 | |
| 3 | Most constraints are treated as walls. This skill treats them as foundations. The limit that |
| 4 | seems like an obstacle is often the thing that forces the insight — the moment you stop |
| 5 | trying to work around it and start designing with it, better solutions appear. |
| 6 | |
| 7 | --- |
| 8 | |
| 9 | ## Your Process |
| 10 | |
| 11 | **Step 1: Name the Constraint Precisely** |
| 12 | State the constraint in a single, unambiguous sentence. Vague constraints produce vague |
| 13 | inversions. "We have no budget" is too loose. "We have $0 for external tooling for Q3" is |
| 14 | something you can work with. |
| 15 | |
| 16 | **Framing check:** Confirm the specific constraint before continuing. State what you've identified — the actual constraint and the goal it is blocking — in one sentence, then use `AskUserQuestion`: |
| 17 | - **Question:** "I'm reading this as: [your one-sentence framing of the constraint and the goal it blocks]. Is that right?" |
| 18 | - **Header:** "Framing" |
| 19 | - **Options:** |
| 20 | - **Yes — proceed** — framing is correct |
| 21 | - **Adjust** — one element is off; user will correct it before you continue |
| 22 | - **Reframe** — different situation than read; incorporate the correction before proceeding |
| 23 | |
| 24 | **Step 2: Ask What the Constraint Forces** |
| 25 | What does this constraint make you do that you'd otherwise avoid? What comfortable defaults |
| 26 | does it eliminate? The constraint is doing work — what work? |
| 27 | |
| 28 | **Step 3: Invert — Restate as a Design Requirement** |
| 29 | Convert the limit into a positive requirement: "must cost nothing" becomes "must work with |
| 30 | only what we already have." The constraint is now the spec, not the problem. |
| 31 | |
| 32 | **Step 4: Generate Solutions That Only Work Because of the Constraint** |
| 33 | Produce 3-5 solutions that are impossible or inferior without the constraint. These are not |
| 34 | workarounds — they are solutions the constraint made visible. |
| 35 | |
| 36 | **Step 5: Select for Unexpected Value** |
| 37 | **Before narrowing:** Show the complete generated set to the user first. Use `AskUserQuestion`: |
| 38 | - **Question:** "I've identified [N] solutions that only work because of the constraint. Before I select the most promising, are there any you'd flag as especially important, or any I've missed?" |
| 39 | - **Header:** "Prioritise" |
| 40 | - **Options:** |
| 41 | - **Proceed with your selection** — the set looks right |
| 42 | - **Flag one** — user will name a specific solution to include |
| 43 | - **Add a missing one** — user will describe it |
| 44 | |
| 45 | Pick the solution where the constraint creates the most unexpected advantage — the one that |
| 46 | would not have been found without the limit. |
| 47 | |
| 48 | --- |
| 49 | |
| 50 | ## Human Check-in |
| 51 | |
| 52 | Before proceeding, use the `AskUserQuestion` tool. State your interpretation of the situation in 1–2 sentences — what is being analyzed and what the core question is — then ask: |
| 53 | |
| 54 | - **Question:** "My read: [your 1–2 sentence interpretation]. How do you want to proceed?" |
| 55 | - **Header:** "Scope" |
| 56 | - **Options:** |
| 57 | - **Full analysis** — Complete all steps, reasoning shown throughout |
| 58 | - **Key findings only** — Bottom-line output, skip step-by-step detail |
| 59 | - **One inversion only** — The single most powerful constraint flip |
| 60 | - **Reframe** — The read is off; correct it and the analysis will follow the corrected framing |
| 61 | |
| 62 | Proceed based on their selection. If the user reframes, incorporate the correction before running any analysis. |
| 63 | |
| 64 | ## Output Format |
| 65 | |
| 66 | **Constraint (precise):** |
| 67 | > [Single sentence, unambiguous] |
| 68 | |
| 69 | **Inverted form (as design requirement):** |
| 70 | > [Positive restatement] |
| 71 | |
| 72 | **Solutions that use the constraint:** |
| 73 | |
| 74 | | # | Solution | Why it requires the constraint | Strength | |
| 75 | |---|----------|-------------------------------|----------| |
| 76 | | 1 | | | | |
| 77 | | 2 | | | | |
| 78 | | 3 | | | | |
| 79 | |
| 80 | **Most promising:** |
| 81 | > [Solution name] — [1-2 sentences on why the constraint creates unexpected value here] |
| 82 | |
| 83 | --- |
| 84 | |
| 85 | ## Notes |
| 86 | |
| 87 | Every analogy breaks somewhere — so does every inversion. If the inverted form produces |
| 88 | solutions that would work equally well without the constraint, the inversion wasn't deep |
| 89 | enough. Go back to Step 2. |
| 90 | |
| 91 | --- |
| 92 | |
| 93 | ## What's Next |
| 94 | |
| 95 | After delivering this output, use `AskUserQuestion` to offer the next move: |
| 96 | |
| 97 | - **Question:** "Rules inverted. What's next?" |
| 98 | - **Header:** "Next" |
| 99 | - **Options:** |
| 100 | - `/s4h-creativity-lateral-thinking` — Use the inverted rules as springboards for lateral moves |
| 101 | - `/s4h-decision-option-mapping` — Map new decision options the inversions open up |
| 102 | - `/s4h-constraint-hardness-testing` — Test whether the inverted rules reveal softer constraints |
| 103 | - **Done** — Wrap up and synthesise what we have so far |