@ckelsoe/prompt-architect 3.0.2 → 3.2.0

package/skills/prompt-architect/assets/templates/ape_template.txt

@@ -1,5 +1,5 @@
-ACTION: [What to do — one clear verb-driven instruction]
-
-PURPOSE: [Why it's needed — one sentence on how it will be used or who needs it]
-
-EXPECTATION: [What a good result looks like — format, length, quality bar, or tone]
+ACTION: [What to do — one clear verb-driven instruction]
+
+PURPOSE: [Why it's needed — one sentence on how it will be used or who needs it]
+
+EXPECTATION: [What a good result looks like — format, length, quality bar, or tone]

package/skills/prompt-architect/assets/templates/bab_template.txt

@@ -1,15 +1,15 @@
-BEFORE:
-[Describe the current state — what exists now, what's wrong with it, what needs to change.
-Be specific: quote actual content, describe current problems, name limitations.]
-
-AFTER:
-[Describe the desired end state — what it should look like once transformed.
-Include: qualities it should have, audience/consumer of the result, success criteria.]
-
-BRIDGE:
-[Define the transformation rules — how to get from Before to After.
-Include:
-- What must be preserved (do not change)
-- What should change
-- Any constraints on approach or style
-- Tone, length, or format requirements for the result]
+BEFORE:
+[Describe the current state — what exists now, what's wrong with it, what needs to change.
+Be specific: quote actual content, describe current problems, name limitations.]
+
+AFTER:
+[Describe the desired end state — what it should look like once transformed.
+Include: qualities it should have, audience/consumer of the result, success criteria.]
+
+BRIDGE:
+[Define the transformation rules — how to get from Before to After.
+Include:
+- What must be preserved (do not change)
+- What should change
+- Any constraints on approach or style
+- Tone, length, or format requirements for the result]

package/skills/prompt-architect/assets/templates/broke_template.txt

@@ -1,15 +1,15 @@
-BACKGROUND:
-[Current situation, why this task exists, relevant history and constraints]
-
-ROLE:
-[Professional persona and expertise to embody]
-
-OBJECTIVE:
-[The specific task and deliverable]
-
-KEY RESULTS:
-[Measurable outcomes this output should help achieve — how success is defined in business terms]
-
-EVOLVE:
-After completing your response, provide 3 specific suggestions for improving
-this output or approach in a follow-up iteration.
+BACKGROUND:
+[Current situation, why this task exists, relevant history and constraints]
+
+ROLE:
+[Professional persona and expertise to embody]
+
+OBJECTIVE:
+[The specific task and deliverable]
+
+KEY RESULTS:
+[Measurable outcomes this output should help achieve — how success is defined in business terms]
+
+EVOLVE:
+After completing your response, provide 3 specific suggestions for improving
+this output or approach in a follow-up iteration.

package/skills/prompt-architect/assets/templates/cai-critique-revise_template.txt

@@ -1,18 +1,18 @@
-PRINCIPLE:
-[State the specific standard the output must satisfy — be precise and measurable]
-
-INITIAL OUTPUT:
-[The output to evaluate — AI-generated or human-written]
-
-CRITIQUE:
-Identify specific ways the output above violates or falls short of the
-principle stated above.
-- Quote the specific passages that are problematic
-- Explain precisely why each passage violates the principle
-- Focus only on failures against the principle (not general quality)
-
-REVISION:
-Rewrite the output to fully satisfy the principle.
-- Address every critique point identified above
-- Preserve all content that already satisfies the principle
-- Do not introduce new violations of the principle
+PRINCIPLE:
+[State the specific standard the output must satisfy — be precise and measurable]
+
+INITIAL OUTPUT:
+[The output to evaluate — AI-generated or human-written]
+
+CRITIQUE:
+Identify specific ways the output above violates or falls short of the
+principle stated above.
+- Quote the specific passages that are problematic
+- Explain precisely why each passage violates the principle
+- Focus only on failures against the principle (not general quality)
+
+REVISION:
+Rewrite the output to fully satisfy the principle.
+- Address every critique point identified above
+- Preserve all content that already satisfies the principle
+- Do not introduce new violations of the principle

package/skills/prompt-architect/assets/templates/care_template.txt

@@ -1,16 +1,16 @@
-CONTEXT:
-[Who you are, the situation you're in, and why this task exists]
-
-ASK:
-[The specific request and deliverable]
-
-RULES:
-[Explicit constraints governing the output:
-- What must be included
-- What must be avoided
-- Format and length requirements
-- Tone and reading level standards
-- Quality bar or compliance requirements]
-
-EXAMPLES:
-[1-3 examples showing the desired output format, tone, or quality standard]
+CONTEXT:
+[Who you are, the situation you're in, and why this task exists]
+
+ASK:
+[The specific request and deliverable]
+
+RULES:
+[Explicit constraints governing the output:
+- What must be included
+- What must be avoided
+- Format and length requirements
+- Tone and reading level standards
+- Quality bar or compliance requirements]
+
+EXAMPLES:
+[1-3 examples showing the desired output format, tone, or quality standard]

package/skills/prompt-architect/assets/templates/chain-of-density_template.txt

@@ -1,46 +1,46 @@
-=== CHAIN OF DENSITY (CoD) TEMPLATE ===
-
-Use when: iterative compression or quality improvement is the goal —
-          summarization, explanation optimization, content densification.
-
-─────────────────────────────────────────────
-SOURCE CONTENT:
-[Paste the content to be refined/compressed here]
-
-─────────────────────────────────────────────
-OPTIMIZATION GOAL:
-[What should improve with each pass?]
-Examples:
-- "Reduce word count by 20% each pass while retaining all key information"
-- "Increase information density — remove filler, make every sentence earn its place"
-- "Improve clarity — each pass should be more direct and easier to understand"
-
-─────────────────────────────────────────────
-NUMBER OF ITERATIONS:
-[How many refinement passes? Typical: 2-4]
-Iteration 1: [First pass — initial improvement]
-Iteration 2: [Second pass — tighten further]
-Iteration 3: [Optional — final polish]
-
-─────────────────────────────────────────────
-ITERATION INSTRUCTIONS:
-For each iteration:
-1. Identify what can be cut, compressed, or clarified
-2. Apply the changes
-3. Verify: does this version better meet the optimization goal than the previous?
-4. Stop when: [define your stopping criterion]
-   Examples: "length < 150 words", "no filler words remain", "3 iterations complete"
-
-─────────────────────────────────────────────
-OUTPUT FORMAT:
-[What format should the final result be in?]
-Examples: paragraph, bullet list, 1-sentence summary, structured sections
-
-─────────────────────────────────────────────
-OPTIONAL — SHOW INTERMEDIATE VERSIONS:
-Set to YES if you want to see each iteration's output.
-Set to NO if you only want the final result.
-
-─────────────────────────────────────────────
-NOTE: Use Self-Refine when the improvement goal is multi-dimensional quality
-(e.g., accuracy + tone + completeness). CoD is specifically for density/compression.
+=== CHAIN OF DENSITY (CoD) TEMPLATE ===
+
+Use when: iterative compression or quality improvement is the goal —
+          summarization, explanation optimization, content densification.
+
+─────────────────────────────────────────────
+SOURCE CONTENT:
+[Paste the content to be refined/compressed here]
+
+─────────────────────────────────────────────
+OPTIMIZATION GOAL:
+[What should improve with each pass?]
+Examples:
+- "Reduce word count by 20% each pass while retaining all key information"
+- "Increase information density — remove filler, make every sentence earn its place"
+- "Improve clarity — each pass should be more direct and easier to understand"
+
+─────────────────────────────────────────────
+NUMBER OF ITERATIONS:
+[How many refinement passes? Typical: 2-4]
+Iteration 1: [First pass — initial improvement]
+Iteration 2: [Second pass — tighten further]
+Iteration 3: [Optional — final polish]
+
+─────────────────────────────────────────────
+ITERATION INSTRUCTIONS:
+For each iteration:
+1. Identify what can be cut, compressed, or clarified
+2. Apply the changes
+3. Verify: does this version better meet the optimization goal than the previous?
+4. Stop when: [define your stopping criterion]
+   Examples: "length < 150 words", "no filler words remain", "3 iterations complete"
+
+─────────────────────────────────────────────
+OUTPUT FORMAT:
+[What format should the final result be in?]
+Examples: paragraph, bullet list, 1-sentence summary, structured sections
+
+─────────────────────────────────────────────
+OPTIONAL — SHOW INTERMEDIATE VERSIONS:
+Set to YES if you want to see each iteration's output.
+Set to NO if you only want the final result.
+
+─────────────────────────────────────────────
+NOTE: Use Self-Refine when the improvement goal is multi-dimensional quality
+(e.g., accuracy + tone + completeness). CoD is specifically for density/compression.

package/skills/prompt-architect/assets/templates/chain-of-thought_template.txt

@@ -1,49 +1,49 @@
-=== CHAIN OF THOUGHT (CoT) TEMPLATE ===
-
-Use when: step-by-step reasoning is needed, logic must be shown,
-          or intermediate conclusions feed into the final answer.
-
-─────────────────────────────────────────────
-PROBLEM / QUESTION:
-[State the problem clearly. Include all relevant numbers, conditions,
-or constraints — everything needed to reason from.]
-
-─────────────────────────────────────────────
-REASONING INSTRUCTION:
-Solve this step-by-step. For each step:
-1. State what you're doing and why
-2. Show your work / intermediate calculation / intermediate conclusion
-3. Verify it before moving to the next step
-
-─────────────────────────────────────────────
-STEPS:
-Step 1: [First reasoning step]
-→ Result: [intermediate conclusion or value]
-
-Step 2: [Next reasoning step, building on Step 1]
-→ Result: [intermediate conclusion or value]
-
-Step 3: [Continue as needed...]
-→ Result: [...]
-
-─────────────────────────────────────────────
-VERIFICATION:
-Before finalizing: check that each step follows logically,
-no conditions were overlooked, and the conclusion matches the question asked.
-
-─────────────────────────────────────────────
-FINAL ANSWER:
-[State the answer clearly after the reasoning chain is complete]
-
-─────────────────────────────────────────────
-TRIGGER VARIANTS (zero-shot alternatives):
-
-Simple:     "Think step by step."
-Explicit:   "Solve this step-by-step, showing your reasoning at each stage."
-Verified:   "Work through this step-by-step, verify each step before continuing,
-             then state your final answer."
-Few-shot:   Prefix with 1-2 worked examples before the actual problem.
-
-NOTE: For numerical/calculation problems, prefer Plan-and-Solve (PS+).
-      For multi-hop problems with dependencies, prefer Least-to-Most.
-      CoT is best for linear step-by-step reasoning on a single problem.
+=== CHAIN OF THOUGHT (CoT) TEMPLATE ===
+
+Use when: step-by-step reasoning is needed, logic must be shown,
+          or intermediate conclusions feed into the final answer.
+
+─────────────────────────────────────────────
+PROBLEM / QUESTION:
+[State the problem clearly. Include all relevant numbers, conditions,
+or constraints — everything needed to reason from.]
+
+─────────────────────────────────────────────
+REASONING INSTRUCTION:
+Solve this step-by-step. For each step:
+1. State what you're doing and why
+2. Show your work / intermediate calculation / intermediate conclusion
+3. Verify it before moving to the next step
+
+─────────────────────────────────────────────
+STEPS:
+Step 1: [First reasoning step]
+→ Result: [intermediate conclusion or value]
+
+Step 2: [Next reasoning step, building on Step 1]
+→ Result: [intermediate conclusion or value]
+
+Step 3: [Continue as needed...]
+→ Result: [...]
+
+─────────────────────────────────────────────
+VERIFICATION:
+Before finalizing: check that each step follows logically,
+no conditions were overlooked, and the conclusion matches the question asked.
+
+─────────────────────────────────────────────
+FINAL ANSWER:
+[State the answer clearly after the reasoning chain is complete]
+
+─────────────────────────────────────────────
+TRIGGER VARIANTS (zero-shot alternatives):
+
+Simple:     "Think step by step."
+Explicit:   "Solve this step-by-step, showing your reasoning at each stage."
+Verified:   "Work through this step-by-step, verify each step before continuing,
+             then state your final answer."
+Few-shot:   Prefix with 1-2 worked examples before the actual problem.
+
+NOTE: For numerical/calculation problems, prefer Plan-and-Solve (PS+).
+      For multi-hop problems with dependencies, prefer Least-to-Most.
+      CoT is best for linear step-by-step reasoning on a single problem.

package/skills/prompt-architect/assets/templates/co-star_template.txt

@@ -1,17 +1,17 @@
-CONTEXT:
-[Provide background information, situation, and any relevant constraints. What's the setting? What's happened before? What limitations exist?]
-
-OBJECTIVE:
-[State the clear, specific goal you want to achieve. What exactly do you want accomplished? What does success look like?]
-
-STYLE:
-[Specify the writing style, format preferences, and structural approach. Should it follow a particular style guide? What format is needed?]
-
-TONE:
-[Define the emotional quality and attitude. Should it be professional, casual, urgent, friendly, authoritative, empathetic, etc.?]
-
-AUDIENCE:
-[Identify who will consume this output. What's their expertise level? What do they care about? What are their characteristics?]
-
-RESPONSE FORMAT:
-[Specify the expected output structure. How long? What sections? What level of detail? Any specific format requirements?]
+CONTEXT:
+[Provide background information, situation, and any relevant constraints. What's the setting? What's happened before? What limitations exist?]
+
+OBJECTIVE:
+[State the clear, specific goal you want to achieve. What exactly do you want accomplished? What does success look like?]
+
+STYLE:
+[Specify the writing style, format preferences, and structural approach. Should it follow a particular style guide? What format is needed?]
+
+TONE:
+[Define the emotional quality and attitude. Should it be professional, casual, urgent, friendly, authoritative, empathetic, etc.?]
+
+AUDIENCE:
+[Identify who will consume this output. What's their expertise level? What do they care about? What are their characteristics?]
+
+RESPONSE FORMAT:
+[Specify the expected output structure. How long? What sections? What level of detail? Any specific format requirements?]

package/skills/prompt-architect/assets/templates/crispe_template.txt

@@ -1,14 +1,14 @@
-CAPACITY AND ROLE:
-[Define the expertise level and professional role to embody — be specific about domain and level]
-
-INSIGHT:
-[Background context, relevant data, constraints, and situational knowledge the AI needs]
-
-INSTRUCTIONS:
-[What exactly needs to be done — the specific task and deliverable]
-
-PERSONALITY (STYLE):
-[Tone, voice, communication style, persona — how the output should sound and feel]
-
-EXPERIMENT:
-[Request N variants along a specific dimension — e.g., "Provide 3 versions: one [X], one [Y], one [Z]"]
+CAPACITY AND ROLE:
+[Define the expertise level and professional role to embody — be specific about domain and level]
+
+INSIGHT:
+[Background context, relevant data, constraints, and situational knowledge the AI needs]
+
+INSTRUCTIONS:
+[What exactly needs to be done — the specific task and deliverable]
+
+PERSONALITY (STYLE):
+[Tone, voice, communication style, persona — how the output should sound and feel]
+
+EXPERIMENT:
+[Request N variants along a specific dimension — e.g., "Provide 3 versions: one [X], one [Y], one [Z]"]

package/skills/prompt-architect/assets/templates/ctf_template.txt

@@ -1,15 +1,15 @@
-CONTEXT:
-[Describe the situation, background, or circumstances surrounding this task.
-Include relevant details like: current state, constraints, what's already been done,
-why this is needed, and any important background the AI should know.]
-
-TASK:
-[State clearly and specifically what needs to be done. Be explicit about the deliverable.]
-
-FORMAT:
-[Specify exactly how the output should be structured:
-- Overall format (document, code, list, table, etc.)
-- Required sections or components
-- Length constraints
-- Style requirements
-- Any specific formatting rules]
+CONTEXT:
+[Describe the situation, background, or circumstances surrounding this task.
+Include relevant details like: current state, constraints, what's already been done,
+why this is needed, and any important background the AI should know.]
+
+TASK:
+[State clearly and specifically what needs to be done. Be explicit about the deliverable.]
+
+FORMAT:
+[Specify exactly how the output should be structured:
+- Overall format (document, code, list, table, etc.)
+- Required sections or components
+- Length constraints
+- Style requirements
+- Any specific formatting rules]

package/skills/prompt-architect/assets/templates/devils-advocate_template.txt

@@ -1,25 +1,25 @@
-You are a rigorous devil's advocate. Your task is NOT to give a balanced view —
-your task is to generate the strongest possible case against the following position.
-
-POSITION TO ATTACK:
-[State the position, plan, decision, or proposal clearly]
-
-ATTACK INSTRUCTIONS:
-- Do not acknowledge positives or offer a balanced view
-- Attack every assumption the position depends on
-- Identify every logical gap or unsupported claim
-- Surface every significant risk or failure mode
-- Point out what better alternatives are being ignored
-- Be as forceful and specific as possible
-
-ATTACK DIMENSIONS:
-Focus on:
-1. Core assumptions (what must be true for this to work?)
-2. Internal logic (where does the reasoning break down?)
-3. Execution risks (what makes this fail in practice?)
-4. Overlooked alternatives (what better options exist?)
-5. [Add domain-specific dimensions as needed]
-
-SEVERITY RANKING:
-After the full attack, list the THREE MOST FATAL flaws — the ones that,
-if unaddressed, would cause this to fail regardless of execution quality.
+You are a rigorous devil's advocate. Your task is NOT to give a balanced view —
+your task is to generate the strongest possible case against the following position.
+
+POSITION TO ATTACK:
+[State the position, plan, decision, or proposal clearly]
+
+ATTACK INSTRUCTIONS:
+- Do not acknowledge positives or offer a balanced view
+- Attack every assumption the position depends on
+- Identify every logical gap or unsupported claim
+- Surface every significant risk or failure mode
+- Point out what better alternatives are being ignored
+- Be as forceful and specific as possible
+
+ATTACK DIMENSIONS:
+Focus on:
+1. Core assumptions (what must be true for this to work?)
+2. Internal logic (where does the reasoning break down?)
+3. Execution risks (what makes this fail in practice?)
+4. Overlooked alternatives (what better options exist?)
+5. [Add domain-specific dimensions as needed]
+
+SEVERITY RANKING:
+After the full attack, list the THREE MOST FATAL flaws — the ones that,
+if unaddressed, would cause this to fail regardless of execution quality.