@ckelsoe/prompt-architect 3.3.1 → 3.4.0

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

@@ -1,33 +1,39 @@
 === CHAIN OF DENSITY (CoD) TEMPLATE ===
 
+Everything down to the first divider rule is guidance for whoever assembles this
+prompt and never belongs in the finished prompt. The prompt itself runs from that
+divider to the end of the file: fill in every bracketed field there, and drop the
+section headers and divider rules when emitting it. 'Step 1.', 'Step 2.' and
+'Guidelines:' are literal labels in this protocol, not headings — keep them exactly
+as written. [TARGET] is the fixed word budget and [N] the number of summaries, both
+as bare numerals; substitute the same numeral at every occurrence of each.
+
 Use when: summarizing a document and you want maximum information in a fixed
           length — articles, papers, reports, executive summaries, abstracts.
 
 NOT for: general rewriting (use Self-Refine), or progressive shortening to a
          target word count (use Iterative Compression). CoD holds length FIXED
-         and raises density. If your text is getting shorter, this is the
+         and raises density — if your text is getting shorter, this is the
          wrong template.
 
 Based on Adams et al., "From Sparse to Dense: GPT-4 Summarization with Chain of
-Density Prompting" (arXiv 2309.04269, NewSum @ EMNLP 2023).
-
-─────────────────────────────────────────────
-SOURCE ARTICLE:
-[Paste the full document to be summarized here]
+Density Prompting" (arXiv 2309.04269, NewSum @ EMNLP 2023). The paper's settings are
+[TARGET] = 80 and [N] = 5; fewer summaries works, more gives diminishing returns. Use
+those if the user gave no numbers of their own.
 
-─────────────────────────────────────────────
-TARGET LENGTH:
-[The fixed word budget every summary must hit. Paper uses ~80 words.]
+The padded first summary is intentional, not a mistake — the filler is the slack that
+later iterations convert into entities. A dense first summary leaves no room and the
+chain stalls.
 
 ─────────────────────────────────────────────
-NUMBER OF ITERATIONS:
-[Paper uses 5. Fewer works; more gives diminishing returns.]
+SOURCE MATERIAL:
+[Paste the full document to be summarized here.]
+Use the material above as the article to be summarized for the work described below.
 
 ─────────────────────────────────────────────
-THE PROMPT — copy from here down, with the fields above filled in:
-
-You will generate increasingly concise, entity-dense summaries of the above
-article.
+You will generate increasingly concise, entity-dense summaries of the article above.
+Produce [N] summaries in total, each denser than the last, all in a single response.
+Every summary must be exactly [TARGET] words long.
 
 Repeat the following 2 steps [N] times.
 
@@ -45,9 +51,9 @@ A missing entity is:
 
 Guidelines:
 - The first summary should be long (4-5 sentences, ~[TARGET] words) yet highly
-  non-specific, containing little information beyond the entities marked as
-  missing. Use overly verbose language and fillers (e.g., "this article
-  discusses") to reach ~[TARGET] words.
+  non-specific, containing little information beyond the entities marked as missing.
+  Use overly verbose language and fillers (e.g., "this article discusses") to reach
+  ~[TARGET] words.
 - Make every word count: re-write the previous summary to improve flow and make
   space for additional entities.
 - Make space with fusion, compression, and removal of uninformative phrases like
@@ -60,17 +66,10 @@ Guidelines:
 
 Remember, use the exact same number of words for each summary.
 
-Answer in JSON. The JSON should be a list (length [N]) of dictionaries whose keys
-are "Missing_Entities" and "Denser_Summary".
-
-─────────────────────────────────────────────
-CHOOSING THE OUTPUT:
-Do not automatically take the last summary. In the paper's human evaluation,
-step 2 (30.8% of first-place votes) and step 3 (23.0%) were preferred over the
-sparse step 1 (8.3%). Past a point, density costs readability. Compare the steps
-and pick deliberately.
+Answer in JSON. The JSON should be a list (length [N]) of dictionaries whose keys are
+"Missing_Entities" and "Denser_Summary".
 
-─────────────────────────────────────────────
-NOTE: The deliberately padded first summary is intentional, not a mistake. The
-filler is the slack that later iterations convert into entities. A dense first
-summary leaves no room and the chain stalls.
+After the JSON, and outside it, add one short paragraph naming which summary you
+recommend and why. Do not default to the last one: in the paper's human evaluation,
+summary 2 (30.8% of first-place votes) and summary 3 (23.0%) were preferred over the
+sparse summary 1 (8.3%), because past a point density costs readability.

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

@@ -8,6 +8,14 @@ PROBLEM / QUESTION:
 [State the problem clearly. Include all relevant numbers, conditions,
 or constraints — everything needed to reason from.]
 
+─────────────────────────────────────────────
+SOURCE MATERIAL:
+[Optional — paste the material the problem refers to here (the code, data,
+document, or transcript to reason over). If the problem stated above is fully
+self-contained, delete this bracketed block and the sentence below it.]
+The reasoning that follows must work from the material above, not from
+assumptions about it.
+
 ─────────────────────────────────────────────
 REASONING INSTRUCTION:
 Solve this step-by-step. For each step:

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

@@ -1,3 +1,11 @@
+SOURCE MATERIAL:
+[OPTIONAL — include only if the content is built from material the user already has.
+If so, emit a literal paste instruction naming the specific artifact, e.g. "[Paste the Q3 revenue report here]"
+or "[Paste the blog post whose voice should be matched here]" — never a generic word like "content" —
+then one line of prose tying it to what follows, e.g. "Use the material above as the factual and stylistic
+basis for what you produce; do not invent details it does not support."
+If the content is written entirely from scratch, omit this section — do not emit an empty placeholder.]
+
 CONTEXT:
 [Provide background information, situation, and any relevant constraints. What's the setting? What's happened before? What limitations exist?]
 

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

@@ -1,3 +1,9 @@
+SOURCE MATERIAL:
+[Optional — paste the material the briefing draws on here, named concretely (the customer
+research deck, the writing sample whose voice should be matched). If you have nothing to
+paste, delete this bracketed block along with the sentence directly below it.]
+Use the material above as the factual and stylistic basis for the work described below.
+
 CAPACITY AND ROLE:
 [Define the expertise level and professional role to embody — be specific about domain and level]
 

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

@@ -1,3 +1,11 @@
+SOURCE MATERIAL:
+[Optional — include only if this task operates on material you already have. Paste the
+specific artifact here and name it in this line, e.g. "Paste the legacy authentication
+function here", "Paste the revised requirements doc here" — the artifact itself, not a
+description of it. If this task generates from scratch, delete this bracketed block along
+with the sentence directly below it.]
+Use the material above as the basis for the task described below.
+
 CONTEXT:
 [Describe the situation, background, or circumstances surrounding this task.
 Include relevant details like: current state, constraints, what's already been done,

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

@@ -4,6 +4,13 @@ your task is to generate the strongest possible case against the following posit
 POSITION TO ATTACK:
 [State the position, plan, decision, or proposal clearly]
 
+SUPPORTING MATERIAL (optional):
+[Optional — paste the proposal, design doc, strategy memo, or other document
+that sets out this position here. If you have nothing to paste, delete this
+bracketed block and the sentence below it.]
+Treat the document above as the detailed source of the position's claims,
+assumptions, and reasoning.
+
 ATTACK INSTRUCTIONS:
 - Do not acknowledge positives or offer a balanced view
 - Attack every assumption the position depends on

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

@@ -1,7 +1,8 @@
 === HYBRID / COMBINED FRAMEWORK TEMPLATE ===
 
-Use this when a single framework doesn't fully cover your needs.
-Include only the sections that add value — remove the rest.
+Use this when a single framework doesn't fully cover your needs. Include only the sections
+that add value and delete the rest — a hybrid with 4 focused sections beats one that uses
+all 15.
 
 ─────────────────────────────────────────────
 COMMON COMBINATION PATTERNS
@@ -35,6 +36,15 @@ Use when: create content → then verify it meets an explicit principle/standard
 HYBRID TEMPLATE STRUCTURE
 ─────────────────────────────────────────────
 
+[Headers are stripped at emission, so fill every slot below with complete sentences that name
+their own subject.]
+
+SOURCE MATERIAL:
+[Optional — paste the artifact this task operates on here, named concretely (the current job
+posting, the Q3 revenue report). If you have nothing to paste, delete this bracketed block
+along with the sentence directly below it.]
+Use the material above as the factual basis for the work described below.
+
 CONTEXT / BACKGROUND:
 [From CTF / CO-STAR / CARE — situation, background, why this task exists]
 
@@ -44,32 +54,42 @@ ROLE:
 OBJECTIVE:
 [From CO-STAR / RISEN — specific goal to achieve]
 
-INPUT (if applicable):
-[From RISE-IE — what's being provided, format, characteristics]
+INPUT CHARACTERISTICS:
+[From RISE-IE's "About the material above" slot — the format, structure, and quirks of
+whatever you pasted under SOURCE MATERIAL, not the material itself. If you pasted nothing
+there, delete this bracketed block.]
 
 INSTRUCTIONS / STEPS:
 [From RISEN / RISE — guiding principles, methodology, step sequence]
 
 CONSTRAINTS / RULES:
-[From CARE / TIDD-EC / RISEN — what must/must not happen, boundaries]
+[From CARE / TIDD-EC / RISEN — boundaries on the work, each stated as a requirement or a
+prohibition]
 
 DO:
-[From TIDD-EC — explicit positive guidance]
+[From TIDD-EC — required behaviors, each a complete imperative sentence]
 
 DON'T:
-[From TIDD-EC — explicit negative guidance]
+[From TIDD-EC — prohibitions, each phrased as "Do not…" or "Never…" so it stands on its own
+line]
 
-AUDIENCE (if relevant):
-[From CO-STAR — who this is for, characteristics]
+AUDIENCE:
+[From CO-STAR — who this is for and what they already know]
 
-TONE & STYLE (if relevant):
+TONE & STYLE:
 [From CO-STAR / CRISPE — voice and communication style]
 
-EXAMPLES (if relevant):
-[From RISE-IX / CARE — reference samples]
+EXAMPLES:
+[From RISE-IX / CARE — reference samples. If you have none, delete this bracketed block along
+with the sentence directly below it.]
+Match the form and quality of the samples above; do not reuse their content.
 
-KEY RESULTS (if relevant):
-[From BROKE — measurable business outcomes]
+KEY RESULTS:
+Your response will be judged on whether it can plausibly move the measurable outcomes
+below. They are the success bar, not tasks to carry out:
+[From BROKE — measurable business outcomes, each a complete sentence naming the metric and
+its target. If the task has no measurable business outcome, delete this bracketed block along
+with the two sentences directly above it.]
 
 END GOAL / EXPECTATION:
 [From RISEN / RACE / BROKE — success criteria, final outcome, output format]
@@ -78,24 +98,24 @@ FORMAT:
 [From RTF / CTF / APE — exactly how output should be structured]
 
 ─────────────────────────────────────────────
-CRITIQUE / VERIFICATION LAYER (optional)
+CRITIQUE / VERIFICATION LAYER
 ─────────────────────────────────────────────
-Add after generation if needed:
+
+[Optional — if the task has a distinct verification phase, keep exactly one of the three
+blocks below and append it after the generation instructions above. Otherwise delete all
+three.]
 
 FEEDBACK DIMENSIONS (Self-Refine):
-Review for: [dimension 1], [dimension 2], [dimension 3]
-Refine addressing all feedback.
+Review your own draft for [dimension 1], [dimension 2], and [dimension 3], then revise it to
+address every point you raised.
 
 OR
 
 PRINCIPLE (CAI Critique-Revise):
-[State the standard] → Critique → Revise.
+Measure your draft against this principle, then revise the draft until it complies: [the
+explicit standard the output must meet].
 
 OR
 
 POSITION ATTACK (Devil's Advocate):
-Argue against the above recommendation as forcefully as possible.
-
-─────────────────────────────────────────────
-NOTE: Use only sections relevant to your task.
-A hybrid with 4 focused sections beats a hybrid that uses all 15.
+Argue against the recommendation above as forcefully as possible.

package/skills/prompt-architect/assets/templates/iterative-compression_template.txt

@@ -1,5 +1,12 @@
 === ITERATIVE COMPRESSION TEMPLATE ===
 
+Everything down to the first divider rule is guidance for whoever assembles this
+prompt and never belongs in the finished prompt. The prompt itself runs from that
+divider to the end of the file: fill in every bracketed field there, and drop the
+section headers and divider rules when emitting it. 'Iteration 1:', 'Iteration 2:'
+and 'Iteration 3:' are literal labels in this protocol, not headings — keep them
+exactly as written wherever they appear.
+
 Use when: text needs to get tighter and shorter through successive passes —
           trimming to a word limit, cutting filler, sharpening explanations.
 
@@ -10,50 +17,58 @@ NOT for: summarization at a FIXED length with rising information density —
          (accuracy + tone + completeness), not compression.
 
 ─────────────────────────────────────────────
-SOURCE CONTENT:
-[Paste the content to be compressed here]
+SOURCE MATERIAL:
+[Paste the full text to be compressed here.]
+Use the material above as the text to be compressed for the work described below.
+Every version must be a rewrite of that material — never introduce a claim it does
+not support.
 
 ─────────────────────────────────────────────
 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"
+Every pass must move the text toward this goal:
+[A full sentence naming what improves and by how much, not a bare label like
+"concision." For example: "Reduce word count by 20% each pass while retaining all key
+information," or "Raise information density — cut filler until every sentence earns
+its place."]
 
 ─────────────────────────────────────────────
 TARGET:
-[Where should this end up? A word count, a reading level, a single paragraph.]
+The final version must reach this end state:
+[A phrase completing the sentence above, e.g. "under 150 words and readable by a
+non-specialist." Name the unit, not a bare number.]
 
 ─────────────────────────────────────────────
 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]
+Run this many passes in total:
+[The count as a phrase completing the sentence above, e.g. "three passes."
+Typical: 2-4]
+Iteration 1: [What this first pass must do to the source text, as a full sentence.]
+Iteration 2: [How this pass tightens the result of pass 1, as a full sentence.]
+Iteration 3: [Optional — what this final polish pass must do, as a full sentence.
+Delete this line if running fewer than three passes; add further Iteration lines in
+the same form if running more.]
 
 ─────────────────────────────────────────────
 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. Confirm nothing essential was lost — compression must not drop content that
-   the goal requires keeping
-5. Stop when: [define your stopping criterion]
-   Examples: "length < 150 words", "no filler words remain", "3 iterations complete"
+In each pass, identify what can be cut, compressed, or clarified, apply the changes,
+then check both that the result serves the goal above better than the version before
+it and that nothing the goal requires keeping was lost. Stop when [a clause completing
+this sentence, e.g. "no filler words remain" or "all three passes are complete"].
 
 ─────────────────────────────────────────────
 OUTPUT FORMAT:
-[What format should the final result be in?]
-Examples: paragraph, bullet list, 1-sentence summary, structured sections
+Deliver the final version in this format:
+[A phrase completing the sentence above, e.g. "a single paragraph of continuous
+prose," a bullet list, or a one-sentence summary.]
 
 ─────────────────────────────────────────────
-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.
+INTERMEDIATE VERSIONS:
+[Optional — keep exactly one of these two sentences as the entire content of this
+block, or delete the block: "Show the output of every iteration in order, labelled by
+pass number." / "Show only the final version — do not print the intermediate
+passes."]
 
 ─────────────────────────────────────────────
-NOTE: Compression has a floor. Past a point, further passes strip meaning rather
-than filler. If an iteration removes something a reader would need, stop at the
-previous version.
+Compression has a floor. Past a point, passes strip meaning rather than filler. If a
+pass would remove something a reader needs, stop at the previous version and deliver
+that.

package/skills/prompt-architect/assets/templates/least-to-most_template.txt

@@ -1,6 +1,10 @@
 PROBLEM:
 [The full, complex problem to solve]
 
+SOURCE MATERIAL:
+[Optional — paste the source material this problem depends on here (the dataset, figures, code, or document the subproblems must reason over). Delete this line and the one below it if the problem above is self-contained.]
+Every subproblem below must be answered against the material above, not from assumption.
+
 DECOMPOSE:
 Break this problem into ordered subproblems, from simplest prerequisite to most complex.
 Each later subproblem should build on the answer to the previous.

package/skills/prompt-architect/assets/templates/plan-and-solve_template.txt

@@ -1,6 +1,10 @@
 PROBLEM:
 [Your question, calculation, or reasoning problem]
 
+SOURCE MATERIAL:
+[Optional — paste the source data the problem depends on here (the dataset, table, figures, or constraint list the calculation runs on). Delete this line and the one below it if the problem above already states every value needed.]
+The figures and constraints in the material above are authoritative — extract from them rather than from assumed or recalled values.
+
 Let's first understand the problem, extract relevant variables and their
 corresponding numerals, and devise a complete plan. Then, let's carry out
 the plan, calculate intermediate values, pay attention to computation,

package/skills/prompt-architect/assets/templates/pre-mortem_template.txt

@@ -1,27 +1,37 @@
-PRE-MORTEM ANALYSIS
+You are conducting a pre-mortem on the project described below. The failure stated further
+down is settled fact, not a possibility — work backwards from it and explain why it happened.
+Do not hedge with "could," "might," or "may."
+
+SOURCE MATERIAL:
+[Optional — paste the project plan, proposal, or decision document here. If you have nothing
+to paste, delete this bracketed block along with the sentence directly below it.]
+Use the material above as the factual basis for the work described below.
 
 PROJECT/DECISION:
-[Describe the project, plan, or decision being analyzed — include team size,
-timeline, resources, key goals, and any relevant constraints]
+[Describe the project, plan, or decision being analyzed in full sentences — what is being
+attempted, plus team size, timeline, resources, goals, and constraints]
 
 FAILURE ASSUMPTION:
-It is [DATE — e.g., 12 months from now] and [project/decision] has completely
-and catastrophically failed. It did not achieve [primary goal].
+It is [DATE — e.g., 12 months from now] and [project/decision] has completely and
+catastrophically failed. It did not achieve [primary goal].
 
 FAILURE NARRATIVE:
-Describe the failure in 2-3 sentences from the perspective of someone
-looking back on it.
+Begin by describing how that failure unfolded, in 2-3 sentences, in past tense from the
+perspective of someone looking back on it.
 
 FAILURE CAUSES:
-Identify [8-12] specific reasons this failed. For each:
+Then identify [8-12] specific reasons it failed, each stated as something that already went
+wrong. Cover technical/product, team/organizational, market/adoption, financial/resource,
+external dependencies, and timeline/scope. Give each cause three lines:
 - CAUSE: [What specifically went wrong — be specific, not generic]
 - DOMAIN: [Technical / People / Market / Financial / External / Timeline]
 - WARNING SIGN: [What was the earliest observable indicator this was happening?]
-
-Cover these domains: technical/product, team/organizational, market/adoption,
-financial/resource, external dependencies, timeline/scope.
+"CAUSE:", "DOMAIN:" and "WARNING SIGN:" are literal labels in this protocol, not headings —
+keep them exactly as written.
 
 PRIORITY ASSESSMENT:
-1. The 3 most LIKELY failure causes given our specific situation
-2. The 3 most PREVENTABLE causes where action now would help most
-3. Any single point of failure that could kill the project alone
+After listing every cause, close by singling out three things:
+1. The 3 causes most LIKELY to be what actually happened, given the situation above.
+2. The 3 most PREVENTABLE causes — where action taken today would have made the most
+   difference.
+3. Any single point of failure that could have killed the project on its own.

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

@@ -1,3 +1,12 @@
+SOURCE MATERIAL:
+[OPTIONAL — include only if this task operates on something the user already has.
+If so, emit a literal paste instruction naming the specific artifact, e.g. "[Paste the REST API design here]"
+or "[Paste the migration plan here]" — then one line of prose tying it to what follows,
+e.g. "The material above is what the task below applies to."
+When this section is used, word ACTION to refer to the material ABOVE ("the migration plan above"),
+never "described below" — the artifact precedes it and a downward reference would dangle.
+If the task generates entirely from scratch, omit this section — do not emit an empty placeholder.]
+
 ROLE:
 [Define the expertise or persona needed — who should do this task and at what level]
 

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

@@ -1,6 +1,14 @@
 STEP 1 — INITIAL ANSWER:
 Answer the following question using step-by-step reasoning. Show your work.
 
+SOURCE MATERIAL:
+[Optional — paste the document the question below is grounded in here (the
+requirements list, contract, specification, or dataset that states the
+conditions to be satisfied). If every condition is already stated in the
+question itself, delete this bracketed block and the sentence directly below
+it.]
+Treat the material above as part of the original question at every step below.
+
 QUESTION:
 [Your question with all conditions and constraints]
 

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

@@ -1,27 +1,49 @@
+You are an agent that reaches a goal by calling tools, not by answering in one pass from what
+you already know. Work in a Thought → Action → Observation loop, letting each real tool result
+decide your next step. If the tools below are not actually callable here, stop and say so —
+without live tools this protocol is only formatted guesswork, and plain step-by-step reasoning
+fits better.
+
 GOAL:
-[Define the end state to achieve — what does success look like?]
+The end state you must reach before you stop:
+[A full sentence naming what must be produced or determined. Write it as an outcome, not an
+activity.]
 
 AVAILABLE TOOLS:
-- [tool_name]: [What it does and how to invoke it]
-- [tool_name]: [What it does and how to invoke it]
-- [tool_name]: [What it does and how to invoke it]
+Do not call any tool that is not named here:
+- [tool_name]: [Full sentence on what this tool does and what input it takes, drawn only from
+  what the user actually told you — do not invent inputs or return values they did not state.]
+- [tool_name]: [Same form, one line per tool the user named. Delete any unused line rather
+  than inventing a tool to fill it.]
 
 CONSTRAINTS:
-- [Rules, limits, or guardrails on actions]
-- [Stop condition: when to stop and deliver Final Answer]
-- [Optional: max iterations or tool call limit]
+Every action is bound by these rules — each is a requirement or a prohibition, not a
+suggestion:
+- [A self-contained imperative, e.g. "Base every conclusion on data you actually retrieved."
+  Phrase restrictions as "Do not…" or "Never…" so each prohibition stands on its own line.]
+- Stop and deliver your Final Answer when [full clause naming the observable situation that
+  means the goal is reached, or that it cannot be].
+- [Optional — a hard ceiling as a full sentence, e.g. "Make no more than 8 tool calls in
+  total." Delete this line if there is no limit.]
 
 APPROACH:
-Use the Thought → Action → Observation cycle until the goal is reached:
+Repeat this cycle until the goal is reached, each step on its own line starting with its
+label. Replace each description below with your actual content:
 
-Thought: [Reason about current state and what to do next]
-Action: [tool_name] — [specific query or operation]
-Observation: [Result of the action]
+Thought: your reasoning about where things stand and what to do next
+Action: the tool name, then an em dash, then the exact input you are passing to that tool
+Observation: the exact result that tool returned
 
-Thought: [Reason about the observation — what does it mean? what to do next?]
-Action: [tool_name] — [next operation]
-Observation: [Result]
+When the cycle has stopped, write this one line, one time only:
 
-[Continue cycling until goal is achieved or stop condition is met]
+Final Answer: the deliverable the goal asked for, supported by what your Observations showed
 
-Final Answer: [Deliver the result once goal is reached]
+Rules for the cycle:
+- Every Action must name one tool from the list above, never prose — e.g. Action:
+  search_docs — "token refresh policy"
+- Take ONE action at a time, then wait for its real Observation before continuing; each
+  Thought must respond to the Observation directly before it.
+- Never write an Observation yourself. An Observation is the actual output of an actual tool
+  call. Inventing one produces a fabricated investigation that reads as though it happened.
+- "Thought:", "Action:", "Observation:" and "Final Answer:" are literal labels in this
+  protocol, not headings — keep them exactly as written.

package/skills/prompt-architect/assets/templates/rise-ie_template.txt

@@ -2,6 +2,10 @@ ROLE:
 [Define the perspective or expertise needed for this task]
 
 INPUT:
+[Paste the data or content to be processed here — name it specifically in this line, e.g.
+"Paste the customer review export (CSV) here". Paste the material itself, not a description of it.]
+
+About the material above:
 [Specify what data/content is being provided:
 - Format and structure (CSV, JSON, text, etc.)
 - Key characteristics and fields

package/skills/prompt-architect/assets/templates/rise-ix_template.txt

@@ -21,8 +21,8 @@ EXAMPLES:
 - Successful outputs from similar tasks
 - 2-3 concrete examples recommended]
 
-Example 1: [First reference example demonstrating desired output]
+Example 1: [Paste the first reference sample here — the actual piece whose style and format the output should match, not a description of it]
 
-Example 2: [Second reference example showing format/style to match]
+Example 2: [Paste a second reference sample here]
 
-[Optional] Example 3: [Third example if additional clarity needed]
+Example 3: [Optional — paste a third reference sample here if more clarity is needed. If you only have two, delete this line and the blank line above it.]

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

@@ -1,3 +1,10 @@
+SOURCE MATERIAL:
+[OPTIONAL — include only if the procedure below operates on something the user already has.
+If so, emit a literal paste instruction naming the specific artifact, e.g. "[Paste the authentication module source here]"
+or "[Paste the Q3 sales dataset here]" — then one line of prose tying it to what follows,
+e.g. "The material above is what the steps below are applied to."
+If the task generates entirely from scratch, omit this section — do not emit an empty placeholder.]
+
 ROLE:
 [Define the expertise level, persona, or perspective to adopt. What knowledge should be demonstrated?]