@ckelsoe/prompt-architect 3.0.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/.claude-plugin/marketplace.json +20 -0
- package/.claude-plugin/plugin.json +18 -0
- package/CHANGELOG.md +264 -0
- package/LICENSE +21 -0
- package/MIGRATION.md +66 -0
- package/README.md +1184 -0
- package/adapters/README.md +267 -0
- package/adapters/for-cursor.mdc +138 -0
- package/adapters/for-gemini-cli.md +70 -0
- package/adapters/for-github-copilot.md +141 -0
- package/adapters/for-openai-codex-cli.md +158 -0
- package/adapters/for-windsurf.md +136 -0
- package/adapters/system-prompt.md +243 -0
- package/package.json +135 -0
- package/scripts/install.js +490 -0
- package/scripts/test.js +213 -0
- package/scripts/validate-skill.js +350 -0
- package/skills/prompt-architect/SKILL.md +331 -0
- package/skills/prompt-architect/assets/templates/ape_template.txt +5 -0
- package/skills/prompt-architect/assets/templates/bab_template.txt +15 -0
- package/skills/prompt-architect/assets/templates/broke_template.txt +15 -0
- package/skills/prompt-architect/assets/templates/cai-critique-revise_template.txt +18 -0
- package/skills/prompt-architect/assets/templates/care_template.txt +16 -0
- package/skills/prompt-architect/assets/templates/chain-of-density_template.txt +46 -0
- package/skills/prompt-architect/assets/templates/chain-of-thought_template.txt +49 -0
- package/skills/prompt-architect/assets/templates/co-star_template.txt +17 -0
- package/skills/prompt-architect/assets/templates/crispe_template.txt +14 -0
- package/skills/prompt-architect/assets/templates/ctf_template.txt +15 -0
- package/skills/prompt-architect/assets/templates/devils-advocate_template.txt +25 -0
- package/skills/prompt-architect/assets/templates/hybrid_template.txt +101 -0
- package/skills/prompt-architect/assets/templates/least-to-most_template.txt +16 -0
- package/skills/prompt-architect/assets/templates/plan-and-solve_template.txt +7 -0
- package/skills/prompt-architect/assets/templates/pre-mortem_template.txt +27 -0
- package/skills/prompt-architect/assets/templates/race_template.txt +19 -0
- package/skills/prompt-architect/assets/templates/rcot_template.txt +31 -0
- package/skills/prompt-architect/assets/templates/react_template.txt +27 -0
- package/skills/prompt-architect/assets/templates/reverse-role_template.txt +11 -0
- package/skills/prompt-architect/assets/templates/rise-ie_template.txt +23 -0
- package/skills/prompt-architect/assets/templates/rise-ix_template.txt +28 -0
- package/skills/prompt-architect/assets/templates/risen_template.txt +21 -0
- package/skills/prompt-architect/assets/templates/rpef_template.txt +26 -0
- package/skills/prompt-architect/assets/templates/rtf_template.txt +13 -0
- package/skills/prompt-architect/assets/templates/self-refine_template.txt +16 -0
- package/skills/prompt-architect/assets/templates/skeleton-of-thought_template.txt +15 -0
- package/skills/prompt-architect/assets/templates/step-back_template.txt +10 -0
- package/skills/prompt-architect/assets/templates/tidd-ec_template.txt +45 -0
- package/skills/prompt-architect/assets/templates/tree-of-thought_template.txt +30 -0
- package/skills/prompt-architect/references/frameworks/ape.md +200 -0
- package/skills/prompt-architect/references/frameworks/bab.md +242 -0
- package/skills/prompt-architect/references/frameworks/broke.md +242 -0
- package/skills/prompt-architect/references/frameworks/cai-critique-revise.md +230 -0
- package/skills/prompt-architect/references/frameworks/care.md +235 -0
- package/skills/prompt-architect/references/frameworks/chain-of-density.md +479 -0
- package/skills/prompt-architect/references/frameworks/chain-of-thought.md +424 -0
- package/skills/prompt-architect/references/frameworks/co-star.md +256 -0
- package/skills/prompt-architect/references/frameworks/crispe.md +253 -0
- package/skills/prompt-architect/references/frameworks/ctf.md +207 -0
- package/skills/prompt-architect/references/frameworks/devils-advocate.md +206 -0
- package/skills/prompt-architect/references/frameworks/least-to-most.md +226 -0
- package/skills/prompt-architect/references/frameworks/plan-and-solve.md +210 -0
- package/skills/prompt-architect/references/frameworks/pre-mortem.md +197 -0
- package/skills/prompt-architect/references/frameworks/race.md +243 -0
- package/skills/prompt-architect/references/frameworks/rcot.md +203 -0
- package/skills/prompt-architect/references/frameworks/react.md +304 -0
- package/skills/prompt-architect/references/frameworks/reverse-role.md +189 -0
- package/skills/prompt-architect/references/frameworks/rise.md +555 -0
- package/skills/prompt-architect/references/frameworks/risen.md +297 -0
- package/skills/prompt-architect/references/frameworks/rpef.md +195 -0
- package/skills/prompt-architect/references/frameworks/rtf.md +358 -0
- package/skills/prompt-architect/references/frameworks/self-refine.md +205 -0
- package/skills/prompt-architect/references/frameworks/skeleton-of-thought.md +186 -0
- package/skills/prompt-architect/references/frameworks/step-back.md +206 -0
- package/skills/prompt-architect/references/frameworks/tidd-ec.md +470 -0
- package/skills/prompt-architect/references/frameworks/tree-of-thought.md +260 -0
- package/skills/prompt-architect/scripts/framework_analyzer.py +807 -0
- package/skills/prompt-architect/scripts/prompt_evaluator.py +336 -0
|
@@ -0,0 +1,15 @@
|
|
|
1
|
+
BEFORE:
|
|
2
|
+
[Describe the current state — what exists now, what's wrong with it, what needs to change.
|
|
3
|
+
Be specific: quote actual content, describe current problems, name limitations.]
|
|
4
|
+
|
|
5
|
+
AFTER:
|
|
6
|
+
[Describe the desired end state — what it should look like once transformed.
|
|
7
|
+
Include: qualities it should have, audience/consumer of the result, success criteria.]
|
|
8
|
+
|
|
9
|
+
BRIDGE:
|
|
10
|
+
[Define the transformation rules — how to get from Before to After.
|
|
11
|
+
Include:
|
|
12
|
+
- What must be preserved (do not change)
|
|
13
|
+
- What should change
|
|
14
|
+
- Any constraints on approach or style
|
|
15
|
+
- Tone, length, or format requirements for the result]
|
|
@@ -0,0 +1,15 @@
|
|
|
1
|
+
BACKGROUND:
|
|
2
|
+
[Current situation, why this task exists, relevant history and constraints]
|
|
3
|
+
|
|
4
|
+
ROLE:
|
|
5
|
+
[Professional persona and expertise to embody]
|
|
6
|
+
|
|
7
|
+
OBJECTIVE:
|
|
8
|
+
[The specific task and deliverable]
|
|
9
|
+
|
|
10
|
+
KEY RESULTS:
|
|
11
|
+
[Measurable outcomes this output should help achieve — how success is defined in business terms]
|
|
12
|
+
|
|
13
|
+
EVOLVE:
|
|
14
|
+
After completing your response, provide 3 specific suggestions for improving
|
|
15
|
+
this output or approach in a follow-up iteration.
|
|
@@ -0,0 +1,18 @@
|
|
|
1
|
+
PRINCIPLE:
|
|
2
|
+
[State the specific standard the output must satisfy — be precise and measurable]
|
|
3
|
+
|
|
4
|
+
INITIAL OUTPUT:
|
|
5
|
+
[The output to evaluate — AI-generated or human-written]
|
|
6
|
+
|
|
7
|
+
CRITIQUE:
|
|
8
|
+
Identify specific ways the output above violates or falls short of the
|
|
9
|
+
principle stated above.
|
|
10
|
+
- Quote the specific passages that are problematic
|
|
11
|
+
- Explain precisely why each passage violates the principle
|
|
12
|
+
- Focus only on failures against the principle (not general quality)
|
|
13
|
+
|
|
14
|
+
REVISION:
|
|
15
|
+
Rewrite the output to fully satisfy the principle.
|
|
16
|
+
- Address every critique point identified above
|
|
17
|
+
- Preserve all content that already satisfies the principle
|
|
18
|
+
- Do not introduce new violations of the principle
|
|
@@ -0,0 +1,16 @@
|
|
|
1
|
+
CONTEXT:
|
|
2
|
+
[Who you are, the situation you're in, and why this task exists]
|
|
3
|
+
|
|
4
|
+
ASK:
|
|
5
|
+
[The specific request and deliverable]
|
|
6
|
+
|
|
7
|
+
RULES:
|
|
8
|
+
[Explicit constraints governing the output:
|
|
9
|
+
- What must be included
|
|
10
|
+
- What must be avoided
|
|
11
|
+
- Format and length requirements
|
|
12
|
+
- Tone and reading level standards
|
|
13
|
+
- Quality bar or compliance requirements]
|
|
14
|
+
|
|
15
|
+
EXAMPLES:
|
|
16
|
+
[1-3 examples showing the desired output format, tone, or quality standard]
|
|
@@ -0,0 +1,46 @@
|
|
|
1
|
+
=== CHAIN OF DENSITY (CoD) TEMPLATE ===
|
|
2
|
+
|
|
3
|
+
Use when: iterative compression or quality improvement is the goal —
|
|
4
|
+
summarization, explanation optimization, content densification.
|
|
5
|
+
|
|
6
|
+
─────────────────────────────────────────────
|
|
7
|
+
SOURCE CONTENT:
|
|
8
|
+
[Paste the content to be refined/compressed here]
|
|
9
|
+
|
|
10
|
+
─────────────────────────────────────────────
|
|
11
|
+
OPTIMIZATION GOAL:
|
|
12
|
+
[What should improve with each pass?]
|
|
13
|
+
Examples:
|
|
14
|
+
- "Reduce word count by 20% each pass while retaining all key information"
|
|
15
|
+
- "Increase information density — remove filler, make every sentence earn its place"
|
|
16
|
+
- "Improve clarity — each pass should be more direct and easier to understand"
|
|
17
|
+
|
|
18
|
+
─────────────────────────────────────────────
|
|
19
|
+
NUMBER OF ITERATIONS:
|
|
20
|
+
[How many refinement passes? Typical: 2-4]
|
|
21
|
+
Iteration 1: [First pass — initial improvement]
|
|
22
|
+
Iteration 2: [Second pass — tighten further]
|
|
23
|
+
Iteration 3: [Optional — final polish]
|
|
24
|
+
|
|
25
|
+
─────────────────────────────────────────────
|
|
26
|
+
ITERATION INSTRUCTIONS:
|
|
27
|
+
For each iteration:
|
|
28
|
+
1. Identify what can be cut, compressed, or clarified
|
|
29
|
+
2. Apply the changes
|
|
30
|
+
3. Verify: does this version better meet the optimization goal than the previous?
|
|
31
|
+
4. Stop when: [define your stopping criterion]
|
|
32
|
+
Examples: "length < 150 words", "no filler words remain", "3 iterations complete"
|
|
33
|
+
|
|
34
|
+
─────────────────────────────────────────────
|
|
35
|
+
OUTPUT FORMAT:
|
|
36
|
+
[What format should the final result be in?]
|
|
37
|
+
Examples: paragraph, bullet list, 1-sentence summary, structured sections
|
|
38
|
+
|
|
39
|
+
─────────────────────────────────────────────
|
|
40
|
+
OPTIONAL — SHOW INTERMEDIATE VERSIONS:
|
|
41
|
+
Set to YES if you want to see each iteration's output.
|
|
42
|
+
Set to NO if you only want the final result.
|
|
43
|
+
|
|
44
|
+
─────────────────────────────────────────────
|
|
45
|
+
NOTE: Use Self-Refine when the improvement goal is multi-dimensional quality
|
|
46
|
+
(e.g., accuracy + tone + completeness). CoD is specifically for density/compression.
|
|
@@ -0,0 +1,49 @@
|
|
|
1
|
+
=== CHAIN OF THOUGHT (CoT) TEMPLATE ===
|
|
2
|
+
|
|
3
|
+
Use when: step-by-step reasoning is needed, logic must be shown,
|
|
4
|
+
or intermediate conclusions feed into the final answer.
|
|
5
|
+
|
|
6
|
+
─────────────────────────────────────────────
|
|
7
|
+
PROBLEM / QUESTION:
|
|
8
|
+
[State the problem clearly. Include all relevant numbers, conditions,
|
|
9
|
+
or constraints — everything needed to reason from.]
|
|
10
|
+
|
|
11
|
+
─────────────────────────────────────────────
|
|
12
|
+
REASONING INSTRUCTION:
|
|
13
|
+
Solve this step-by-step. For each step:
|
|
14
|
+
1. State what you're doing and why
|
|
15
|
+
2. Show your work / intermediate calculation / intermediate conclusion
|
|
16
|
+
3. Verify it before moving to the next step
|
|
17
|
+
|
|
18
|
+
─────────────────────────────────────────────
|
|
19
|
+
STEPS:
|
|
20
|
+
Step 1: [First reasoning step]
|
|
21
|
+
→ Result: [intermediate conclusion or value]
|
|
22
|
+
|
|
23
|
+
Step 2: [Next reasoning step, building on Step 1]
|
|
24
|
+
→ Result: [intermediate conclusion or value]
|
|
25
|
+
|
|
26
|
+
Step 3: [Continue as needed...]
|
|
27
|
+
→ Result: [...]
|
|
28
|
+
|
|
29
|
+
─────────────────────────────────────────────
|
|
30
|
+
VERIFICATION:
|
|
31
|
+
Before finalizing: check that each step follows logically,
|
|
32
|
+
no conditions were overlooked, and the conclusion matches the question asked.
|
|
33
|
+
|
|
34
|
+
─────────────────────────────────────────────
|
|
35
|
+
FINAL ANSWER:
|
|
36
|
+
[State the answer clearly after the reasoning chain is complete]
|
|
37
|
+
|
|
38
|
+
─────────────────────────────────────────────
|
|
39
|
+
TRIGGER VARIANTS (zero-shot alternatives):
|
|
40
|
+
|
|
41
|
+
Simple: "Think step by step."
|
|
42
|
+
Explicit: "Solve this step-by-step, showing your reasoning at each stage."
|
|
43
|
+
Verified: "Work through this step-by-step, verify each step before continuing,
|
|
44
|
+
then state your final answer."
|
|
45
|
+
Few-shot: Prefix with 1-2 worked examples before the actual problem.
|
|
46
|
+
|
|
47
|
+
NOTE: For numerical/calculation problems, prefer Plan-and-Solve (PS+).
|
|
48
|
+
For multi-hop problems with dependencies, prefer Least-to-Most.
|
|
49
|
+
CoT is best for linear step-by-step reasoning on a single problem.
|
|
@@ -0,0 +1,17 @@
|
|
|
1
|
+
CONTEXT:
|
|
2
|
+
[Provide background information, situation, and any relevant constraints. What's the setting? What's happened before? What limitations exist?]
|
|
3
|
+
|
|
4
|
+
OBJECTIVE:
|
|
5
|
+
[State the clear, specific goal you want to achieve. What exactly do you want accomplished? What does success look like?]
|
|
6
|
+
|
|
7
|
+
STYLE:
|
|
8
|
+
[Specify the writing style, format preferences, and structural approach. Should it follow a particular style guide? What format is needed?]
|
|
9
|
+
|
|
10
|
+
TONE:
|
|
11
|
+
[Define the emotional quality and attitude. Should it be professional, casual, urgent, friendly, authoritative, empathetic, etc.?]
|
|
12
|
+
|
|
13
|
+
AUDIENCE:
|
|
14
|
+
[Identify who will consume this output. What's their expertise level? What do they care about? What are their characteristics?]
|
|
15
|
+
|
|
16
|
+
RESPONSE FORMAT:
|
|
17
|
+
[Specify the expected output structure. How long? What sections? What level of detail? Any specific format requirements?]
|
|
@@ -0,0 +1,14 @@
|
|
|
1
|
+
CAPACITY AND ROLE:
|
|
2
|
+
[Define the expertise level and professional role to embody — be specific about domain and level]
|
|
3
|
+
|
|
4
|
+
INSIGHT:
|
|
5
|
+
[Background context, relevant data, constraints, and situational knowledge the AI needs]
|
|
6
|
+
|
|
7
|
+
INSTRUCTIONS:
|
|
8
|
+
[What exactly needs to be done — the specific task and deliverable]
|
|
9
|
+
|
|
10
|
+
PERSONALITY (STYLE):
|
|
11
|
+
[Tone, voice, communication style, persona — how the output should sound and feel]
|
|
12
|
+
|
|
13
|
+
EXPERIMENT:
|
|
14
|
+
[Request N variants along a specific dimension — e.g., "Provide 3 versions: one [X], one [Y], one [Z]"]
|
|
@@ -0,0 +1,15 @@
|
|
|
1
|
+
CONTEXT:
|
|
2
|
+
[Describe the situation, background, or circumstances surrounding this task.
|
|
3
|
+
Include relevant details like: current state, constraints, what's already been done,
|
|
4
|
+
why this is needed, and any important background the AI should know.]
|
|
5
|
+
|
|
6
|
+
TASK:
|
|
7
|
+
[State clearly and specifically what needs to be done. Be explicit about the deliverable.]
|
|
8
|
+
|
|
9
|
+
FORMAT:
|
|
10
|
+
[Specify exactly how the output should be structured:
|
|
11
|
+
- Overall format (document, code, list, table, etc.)
|
|
12
|
+
- Required sections or components
|
|
13
|
+
- Length constraints
|
|
14
|
+
- Style requirements
|
|
15
|
+
- Any specific formatting rules]
|
|
@@ -0,0 +1,25 @@
|
|
|
1
|
+
You are a rigorous devil's advocate. Your task is NOT to give a balanced view —
|
|
2
|
+
your task is to generate the strongest possible case against the following position.
|
|
3
|
+
|
|
4
|
+
POSITION TO ATTACK:
|
|
5
|
+
[State the position, plan, decision, or proposal clearly]
|
|
6
|
+
|
|
7
|
+
ATTACK INSTRUCTIONS:
|
|
8
|
+
- Do not acknowledge positives or offer a balanced view
|
|
9
|
+
- Attack every assumption the position depends on
|
|
10
|
+
- Identify every logical gap or unsupported claim
|
|
11
|
+
- Surface every significant risk or failure mode
|
|
12
|
+
- Point out what better alternatives are being ignored
|
|
13
|
+
- Be as forceful and specific as possible
|
|
14
|
+
|
|
15
|
+
ATTACK DIMENSIONS:
|
|
16
|
+
Focus on:
|
|
17
|
+
1. Core assumptions (what must be true for this to work?)
|
|
18
|
+
2. Internal logic (where does the reasoning break down?)
|
|
19
|
+
3. Execution risks (what makes this fail in practice?)
|
|
20
|
+
4. Overlooked alternatives (what better options exist?)
|
|
21
|
+
5. [Add domain-specific dimensions as needed]
|
|
22
|
+
|
|
23
|
+
SEVERITY RANKING:
|
|
24
|
+
After the full attack, list the THREE MOST FATAL flaws — the ones that,
|
|
25
|
+
if unaddressed, would cause this to fail regardless of execution quality.
|
|
@@ -0,0 +1,101 @@
|
|
|
1
|
+
=== HYBRID / COMBINED FRAMEWORK TEMPLATE ===
|
|
2
|
+
|
|
3
|
+
Use this when a single framework doesn't fully cover your needs.
|
|
4
|
+
Include only the sections that add value — remove the rest.
|
|
5
|
+
|
|
6
|
+
─────────────────────────────────────────────
|
|
7
|
+
COMMON COMBINATION PATTERNS
|
|
8
|
+
─────────────────────────────────────────────
|
|
9
|
+
|
|
10
|
+
[REQUIREMENTS GATHERING → EXECUTION]
|
|
11
|
+
Reverse Role (interview) → any CREATE framework
|
|
12
|
+
Use when: requirements unclear → gather first → then apply CO-STAR/RISEN/RACE/etc.
|
|
13
|
+
|
|
14
|
+
[STRESS-TEST PAIR]
|
|
15
|
+
Devil's Advocate + Pre-Mortem
|
|
16
|
+
Use when: high-stakes decision needs both opposing arguments AND failure analysis
|
|
17
|
+
|
|
18
|
+
[TRANSFORM THEN VERIFY]
|
|
19
|
+
BAB + Self-Refine
|
|
20
|
+
Use when: rewrite existing content → then quality-loop the result
|
|
21
|
+
|
|
22
|
+
[PRINCIPLES THEN EXECUTE]
|
|
23
|
+
Step-Back + Chain of Thought
|
|
24
|
+
Use when: need to establish first principles before working through a problem
|
|
25
|
+
|
|
26
|
+
[RECOVER THEN IMPROVE]
|
|
27
|
+
RPEF + Self-Refine
|
|
28
|
+
Use when: recover a lost prompt → then improve the recovered template
|
|
29
|
+
|
|
30
|
+
[GENERATE THEN ALIGN]
|
|
31
|
+
CO-STAR/RISEN + CAI Critique-Revise
|
|
32
|
+
Use when: create content → then verify it meets an explicit principle/standard
|
|
33
|
+
|
|
34
|
+
─────────────────────────────────────────────
|
|
35
|
+
HYBRID TEMPLATE STRUCTURE
|
|
36
|
+
─────────────────────────────────────────────
|
|
37
|
+
|
|
38
|
+
CONTEXT / BACKGROUND:
|
|
39
|
+
[From CTF / CO-STAR / CARE — situation, background, why this task exists]
|
|
40
|
+
|
|
41
|
+
ROLE:
|
|
42
|
+
[From RTF / RISEN / RACE / CRISPE — expertise or perspective needed]
|
|
43
|
+
|
|
44
|
+
OBJECTIVE:
|
|
45
|
+
[From CO-STAR / RISEN — specific goal to achieve]
|
|
46
|
+
|
|
47
|
+
INPUT (if applicable):
|
|
48
|
+
[From RISE-IE — what's being provided, format, characteristics]
|
|
49
|
+
|
|
50
|
+
INSTRUCTIONS / STEPS:
|
|
51
|
+
[From RISEN / RISE — guiding principles, methodology, step sequence]
|
|
52
|
+
|
|
53
|
+
CONSTRAINTS / RULES:
|
|
54
|
+
[From CARE / TIDD-EC / RISEN — what must/must not happen, boundaries]
|
|
55
|
+
|
|
56
|
+
DO:
|
|
57
|
+
[From TIDD-EC — explicit positive guidance]
|
|
58
|
+
|
|
59
|
+
DON'T:
|
|
60
|
+
[From TIDD-EC — explicit negative guidance]
|
|
61
|
+
|
|
62
|
+
AUDIENCE (if relevant):
|
|
63
|
+
[From CO-STAR — who this is for, characteristics]
|
|
64
|
+
|
|
65
|
+
TONE & STYLE (if relevant):
|
|
66
|
+
[From CO-STAR / CRISPE — voice and communication style]
|
|
67
|
+
|
|
68
|
+
EXAMPLES (if relevant):
|
|
69
|
+
[From RISE-IX / CARE — reference samples]
|
|
70
|
+
|
|
71
|
+
KEY RESULTS (if relevant):
|
|
72
|
+
[From BROKE — measurable business outcomes]
|
|
73
|
+
|
|
74
|
+
END GOAL / EXPECTATION:
|
|
75
|
+
[From RISEN / RACE / BROKE — success criteria, final outcome, output format]
|
|
76
|
+
|
|
77
|
+
FORMAT:
|
|
78
|
+
[From RTF / CTF / APE — exactly how output should be structured]
|
|
79
|
+
|
|
80
|
+
─────────────────────────────────────────────
|
|
81
|
+
CRITIQUE / VERIFICATION LAYER (optional)
|
|
82
|
+
─────────────────────────────────────────────
|
|
83
|
+
Add after generation if needed:
|
|
84
|
+
|
|
85
|
+
FEEDBACK DIMENSIONS (Self-Refine):
|
|
86
|
+
Review for: [dimension 1], [dimension 2], [dimension 3]
|
|
87
|
+
Refine addressing all feedback.
|
|
88
|
+
|
|
89
|
+
OR
|
|
90
|
+
|
|
91
|
+
PRINCIPLE (CAI Critique-Revise):
|
|
92
|
+
[State the standard] → Critique → Revise.
|
|
93
|
+
|
|
94
|
+
OR
|
|
95
|
+
|
|
96
|
+
POSITION ATTACK (Devil's Advocate):
|
|
97
|
+
Argue against the above recommendation as forcefully as possible.
|
|
98
|
+
|
|
99
|
+
─────────────────────────────────────────────
|
|
100
|
+
NOTE: Use only sections relevant to your task.
|
|
101
|
+
A hybrid with 4 focused sections beats a hybrid that uses all 15.
|
|
@@ -0,0 +1,16 @@
|
|
|
1
|
+
PROBLEM:
|
|
2
|
+
[The full, complex problem to solve]
|
|
3
|
+
|
|
4
|
+
DECOMPOSE:
|
|
5
|
+
Break this problem into ordered subproblems, from simplest prerequisite to most complex.
|
|
6
|
+
Each later subproblem should build on the answer to the previous.
|
|
7
|
+
|
|
8
|
+
Subproblem 1: [Simplest prerequisite — must be answered first]
|
|
9
|
+
Subproblem 2: [Builds on #1]
|
|
10
|
+
Subproblem 3: [Builds on #1-2]
|
|
11
|
+
[Add subproblems as needed]
|
|
12
|
+
Final: [The original problem, now solvable using all prior answers]
|
|
13
|
+
|
|
14
|
+
SOLVE SEQUENTIALLY:
|
|
15
|
+
Solve each subproblem in order. Use prior answers explicitly as context
|
|
16
|
+
for each subsequent subproblem. Show each solution before moving to the next.
|
|
@@ -0,0 +1,7 @@
|
|
|
1
|
+
PROBLEM:
|
|
2
|
+
[Your question, calculation, or reasoning problem]
|
|
3
|
+
|
|
4
|
+
Let's first understand the problem, extract relevant variables and their
|
|
5
|
+
corresponding numerals, and devise a complete plan. Then, let's carry out
|
|
6
|
+
the plan, calculate intermediate values, pay attention to computation,
|
|
7
|
+
and solve the problem step by step.
|
|
@@ -0,0 +1,27 @@
|
|
|
1
|
+
PRE-MORTEM ANALYSIS
|
|
2
|
+
|
|
3
|
+
PROJECT/DECISION:
|
|
4
|
+
[Describe the project, plan, or decision being analyzed — include team size,
|
|
5
|
+
timeline, resources, key goals, and any relevant constraints]
|
|
6
|
+
|
|
7
|
+
FAILURE ASSUMPTION:
|
|
8
|
+
It is [DATE — e.g., 12 months from now] and [project/decision] has completely
|
|
9
|
+
and catastrophically failed. It did not achieve [primary goal].
|
|
10
|
+
|
|
11
|
+
FAILURE NARRATIVE:
|
|
12
|
+
Describe the failure in 2-3 sentences from the perspective of someone
|
|
13
|
+
looking back on it.
|
|
14
|
+
|
|
15
|
+
FAILURE CAUSES:
|
|
16
|
+
Identify [8-12] specific reasons this failed. For each:
|
|
17
|
+
- CAUSE: [What specifically went wrong — be specific, not generic]
|
|
18
|
+
- DOMAIN: [Technical / People / Market / Financial / External / Timeline]
|
|
19
|
+
- WARNING SIGN: [What was the earliest observable indicator this was happening?]
|
|
20
|
+
|
|
21
|
+
Cover these domains: technical/product, team/organizational, market/adoption,
|
|
22
|
+
financial/resource, external dependencies, timeline/scope.
|
|
23
|
+
|
|
24
|
+
PRIORITY ASSESSMENT:
|
|
25
|
+
1. The 3 most LIKELY failure causes given our specific situation
|
|
26
|
+
2. The 3 most PREVENTABLE causes where action now would help most
|
|
27
|
+
3. Any single point of failure that could kill the project alone
|
|
@@ -0,0 +1,19 @@
|
|
|
1
|
+
ROLE:
|
|
2
|
+
[Define the expertise or persona needed — who should do this task and at what level]
|
|
3
|
+
|
|
4
|
+
ACTION:
|
|
5
|
+
[State clearly what needs to be done — the task and deliverable]
|
|
6
|
+
|
|
7
|
+
CONTEXT:
|
|
8
|
+
[Provide the situational background:
|
|
9
|
+
- What's the current state / situation?
|
|
10
|
+
- Who is the audience or recipient of the output?
|
|
11
|
+
- Any relevant constraints or prior decisions?
|
|
12
|
+
- What has already been done?]
|
|
13
|
+
|
|
14
|
+
EXPECTATION:
|
|
15
|
+
[Define what a successful output looks like:
|
|
16
|
+
- Format and structure requirements
|
|
17
|
+
- Quality bar or success criteria
|
|
18
|
+
- What should be prioritized
|
|
19
|
+
- Length or scope constraints]
|
|
@@ -0,0 +1,31 @@
|
|
|
1
|
+
STEP 1 — INITIAL ANSWER:
|
|
2
|
+
Answer the following question using step-by-step reasoning. Show your work.
|
|
3
|
+
|
|
4
|
+
QUESTION:
|
|
5
|
+
[Your question with all conditions and constraints]
|
|
6
|
+
|
|
7
|
+
---
|
|
8
|
+
|
|
9
|
+
STEP 2 — QUESTION RECONSTRUCTION:
|
|
10
|
+
Looking only at your answer above (do not re-read the original question),
|
|
11
|
+
reconstruct the question that would produce this answer.
|
|
12
|
+
List every condition, constraint, and piece of information the question
|
|
13
|
+
must have contained.
|
|
14
|
+
|
|
15
|
+
---
|
|
16
|
+
|
|
17
|
+
STEP 3 — CROSS-CHECK:
|
|
18
|
+
Now compare your reconstructed question to the actual original question.
|
|
19
|
+
Identify:
|
|
20
|
+
- Conditions in the ORIGINAL question MISSING from your reconstruction
|
|
21
|
+
(these are conditions you overlooked in your reasoning)
|
|
22
|
+
- Conditions in your RECONSTRUCTION not in the original question
|
|
23
|
+
(assumptions you made that weren't stated)
|
|
24
|
+
- Conditions present in both but interpreted differently
|
|
25
|
+
|
|
26
|
+
---
|
|
27
|
+
|
|
28
|
+
STEP 4 — CORRECTION:
|
|
29
|
+
If discrepancies were found, generate a corrected answer that addresses
|
|
30
|
+
every condition in the original question.
|
|
31
|
+
If no discrepancies, confirm the original answer is correct.
|
|
@@ -0,0 +1,27 @@
|
|
|
1
|
+
GOAL:
|
|
2
|
+
[Define the end state to achieve — what does success look like?]
|
|
3
|
+
|
|
4
|
+
AVAILABLE TOOLS:
|
|
5
|
+
- [tool_name]: [What it does and how to invoke it]
|
|
6
|
+
- [tool_name]: [What it does and how to invoke it]
|
|
7
|
+
- [tool_name]: [What it does and how to invoke it]
|
|
8
|
+
|
|
9
|
+
CONSTRAINTS:
|
|
10
|
+
- [Rules, limits, or guardrails on actions]
|
|
11
|
+
- [Stop condition: when to stop and deliver Final Answer]
|
|
12
|
+
- [Optional: max iterations or tool call limit]
|
|
13
|
+
|
|
14
|
+
APPROACH:
|
|
15
|
+
Use the Thought → Action → Observation cycle until the goal is reached:
|
|
16
|
+
|
|
17
|
+
Thought: [Reason about current state and what to do next]
|
|
18
|
+
Action: [tool_name] — [specific query or operation]
|
|
19
|
+
Observation: [Result of the action]
|
|
20
|
+
|
|
21
|
+
Thought: [Reason about the observation — what does it mean? what to do next?]
|
|
22
|
+
Action: [tool_name] — [next operation]
|
|
23
|
+
Observation: [Result]
|
|
24
|
+
|
|
25
|
+
[Continue cycling until goal is achieved or stop condition is met]
|
|
26
|
+
|
|
27
|
+
Final Answer: [Deliver the result once goal is reached]
|
|
@@ -0,0 +1,11 @@
|
|
|
1
|
+
You are an expert [DOMAIN] consultant / specialist.
|
|
2
|
+
|
|
3
|
+
My goal: [1-2 sentence description of what you want to achieve]
|
|
4
|
+
|
|
5
|
+
Before you begin, interview me to understand my specific context, constraints,
|
|
6
|
+
goals, and any relevant background. Ask your questions [one at a time / all at once].
|
|
7
|
+
Only proceed with [the task / generating the full prompt] once you are confident
|
|
8
|
+
you have everything you need.
|
|
9
|
+
|
|
10
|
+
[Optional: After the interview, synthesize my responses into a complete structured
|
|
11
|
+
prompt using the most appropriate framework, then confirm before executing.]
|
|
@@ -0,0 +1,23 @@
|
|
|
1
|
+
ROLE:
|
|
2
|
+
[Define the perspective or expertise needed for this task]
|
|
3
|
+
|
|
4
|
+
INPUT:
|
|
5
|
+
[Specify what data/content is being provided:
|
|
6
|
+
- Format and structure (CSV, JSON, text, etc.)
|
|
7
|
+
- Key characteristics and fields
|
|
8
|
+
- Any quirks or special considerations
|
|
9
|
+
- What to expect in the data]
|
|
10
|
+
|
|
11
|
+
STEPS:
|
|
12
|
+
1. [How to process the input - first action]
|
|
13
|
+
2. [Processing step 2 - transformation or analysis]
|
|
14
|
+
3. [Processing step 3 - continue with methodology]
|
|
15
|
+
4. [Add more processing/analysis steps as needed...]
|
|
16
|
+
|
|
17
|
+
EXPECTATION:
|
|
18
|
+
[Define what the output should look like:
|
|
19
|
+
- Format and structure
|
|
20
|
+
- Required elements and sections
|
|
21
|
+
- Level of detail needed
|
|
22
|
+
- Length or size constraints
|
|
23
|
+
- Specific deliverables]
|
|
@@ -0,0 +1,28 @@
|
|
|
1
|
+
ROLE:
|
|
2
|
+
[Define who the AI should embody - persona or expertise level]
|
|
3
|
+
|
|
4
|
+
INSTRUCTIONS:
|
|
5
|
+
[Specify the main task or directive:
|
|
6
|
+
- What to create or accomplish
|
|
7
|
+
- Core requirements
|
|
8
|
+
- Key guidelines to follow
|
|
9
|
+
- Specific constraints or considerations]
|
|
10
|
+
|
|
11
|
+
STEPS:
|
|
12
|
+
1. [Approach or methodology step 1]
|
|
13
|
+
2. [Step 2 - how to execute the task]
|
|
14
|
+
3. [Step 3 - continue with workflow]
|
|
15
|
+
4. [Add more steps as needed for the creative/instruction process...]
|
|
16
|
+
|
|
17
|
+
EXAMPLES:
|
|
18
|
+
[Provide positive examples showing desired output:
|
|
19
|
+
- Reference materials that demonstrate the style
|
|
20
|
+
- Format examples to emulate
|
|
21
|
+
- Successful outputs from similar tasks
|
|
22
|
+
- 2-3 concrete examples recommended]
|
|
23
|
+
|
|
24
|
+
Example 1: [First reference example demonstrating desired output]
|
|
25
|
+
|
|
26
|
+
Example 2: [Second reference example showing format/style to match]
|
|
27
|
+
|
|
28
|
+
[Optional] Example 3: [Third example if additional clarity needed]
|
|
@@ -0,0 +1,21 @@
|
|
|
1
|
+
ROLE:
|
|
2
|
+
[Define the expertise level, persona, or perspective to adopt. What knowledge should be demonstrated?]
|
|
3
|
+
|
|
4
|
+
INSTRUCTIONS:
|
|
5
|
+
[Provide high-level guidance, principles, and overarching direction. What methodology or approach should guide this work?]
|
|
6
|
+
|
|
7
|
+
STEPS:
|
|
8
|
+
1. [First specific action or stage]
|
|
9
|
+
2. [Second specific action or stage]
|
|
10
|
+
3. [Third specific action or stage]
|
|
11
|
+
[Continue with detailed, sequential steps...]
|
|
12
|
+
|
|
13
|
+
END GOAL:
|
|
14
|
+
[Define success criteria and final desired outcome. What should be true when complete? How will we know it's done correctly?]
|
|
15
|
+
|
|
16
|
+
NARROWING:
|
|
17
|
+
- Do NOT: [Specific thing to avoid]
|
|
18
|
+
- Avoid: [Approach or pattern to avoid]
|
|
19
|
+
- Out of scope: [What's not included]
|
|
20
|
+
- Stay within: [Boundaries and constraints]
|
|
21
|
+
- Constraints: [Limitations to respect]
|
|
@@ -0,0 +1,26 @@
|
|
|
1
|
+
You are an expert Prompt Engineer performing reverse prompt engineering.
|
|
2
|
+
|
|
3
|
+
TASK:
|
|
4
|
+
Analyze the following [input and] output. Reconstruct the prompt that would
|
|
5
|
+
consistently produce this type of output. Your recovered prompt should be
|
|
6
|
+
reusable — replace specific details with clearly marked [PLACEHOLDER] variables.
|
|
7
|
+
|
|
8
|
+
[INPUT DATA (if applicable — omit if output-only):]
|
|
9
|
+
[Paste the input that produced the output, or remove this section]
|
|
10
|
+
|
|
11
|
+
OUTPUT SAMPLE:
|
|
12
|
+
[Paste the output you want to reverse-engineer]
|
|
13
|
+
|
|
14
|
+
ANALYSIS INSTRUCTIONS:
|
|
15
|
+
Examine the output for:
|
|
16
|
+
- Implied role or persona
|
|
17
|
+
- Tone and voice
|
|
18
|
+
- Structural and formatting patterns
|
|
19
|
+
- Level of detail and scope
|
|
20
|
+
- Implicit constraints (what it did NOT do)
|
|
21
|
+
- Reasoning style
|
|
22
|
+
|
|
23
|
+
RECOVERED PROMPT:
|
|
24
|
+
Generate a reusable prompt template that reliably reproduces this type of output.
|
|
25
|
+
Use [PLACEHOLDER] for variable elements.
|
|
26
|
+
Only proceed when at least 80% confident in the reconstruction.
|
|
@@ -0,0 +1,13 @@
|
|
|
1
|
+
ROLE:
|
|
2
|
+
[Define the expertise or perspective needed for this task]
|
|
3
|
+
|
|
4
|
+
TASK:
|
|
5
|
+
[State clearly and specifically what needs to be done. Be explicit about the deliverable.]
|
|
6
|
+
|
|
7
|
+
FORMAT:
|
|
8
|
+
[Specify exactly how the output should be structured:
|
|
9
|
+
- Overall format (document, code, list, table, etc.)
|
|
10
|
+
- Required sections or components
|
|
11
|
+
- Length constraints
|
|
12
|
+
- Style requirements
|
|
13
|
+
- Any specific formatting rules]
|
|
@@ -0,0 +1,16 @@
|
|
|
1
|
+
INITIAL OUTPUT:
|
|
2
|
+
[Paste the output to improve, or ask the AI to generate a first draft here]
|
|
3
|
+
|
|
4
|
+
FEEDBACK DIMENSIONS:
|
|
5
|
+
Review the output above for:
|
|
6
|
+
1. [Dimension 1 — e.g., "Clarity: Are there any ambiguous or hard-to-parse sentences?"]
|
|
7
|
+
2. [Dimension 2 — e.g., "Completeness: What important points are missing?"]
|
|
8
|
+
3. [Dimension 3 — e.g., "Tone: Is the voice appropriate for the audience?"]
|
|
9
|
+
4. [Dimension 4 — add or remove as needed]
|
|
10
|
+
|
|
11
|
+
For each dimension: quote specific problematic passages, explain the issue,
|
|
12
|
+
and suggest a concrete improvement.
|
|
13
|
+
|
|
14
|
+
REFINEMENT:
|
|
15
|
+
Rewrite the output addressing every point of your feedback above.
|
|
16
|
+
Show the refined version only.
|
|
@@ -0,0 +1,15 @@
|
|
|
1
|
+
PHASE 1 — SKELETON:
|
|
2
|
+
Generate a skeleton outline for the following topic or question.
|
|
3
|
+
List only the key points — one per line — in this format:
|
|
4
|
+
N. [Point name] | [One-sentence description of what this point covers]
|
|
5
|
+
Do not expand yet. Skeleton only.
|
|
6
|
+
|
|
7
|
+
TOPIC / QUESTION:
|
|
8
|
+
[Your topic or question]
|
|
9
|
+
|
|
10
|
+
---
|
|
11
|
+
|
|
12
|
+
PHASE 2 — EXPAND:
|
|
13
|
+
Now expand each skeleton point into [2-4 sentences / a paragraph / detailed coverage].
|
|
14
|
+
Each point should be self-contained and complete.
|
|
15
|
+
[Optional: expand points in parallel by sending each as a separate API call]
|
|
@@ -0,0 +1,10 @@
|
|
|
1
|
+
ORIGINAL QUESTION:
|
|
2
|
+
[The specific question you want answered]
|
|
3
|
+
|
|
4
|
+
STEP-BACK:
|
|
5
|
+
Before answering directly, first answer this higher-level question:
|
|
6
|
+
[Rephrase the original into a more abstract question about underlying principles, concepts, or rules]
|
|
7
|
+
|
|
8
|
+
PRINCIPLE APPLICATION:
|
|
9
|
+
Using the principles/concepts you just described, now answer the original question:
|
|
10
|
+
[Restate original question here]
|