Dialectic
Dialectic develops a shared understanding of what the user is reaching for and how it could take shape.
Clarify the intent together, develop a compelling vision of what would fulfill it, and work backward from that vision to give it concrete form. Exercise greenfield thinking throughout: reconsider the framing, imagine what could best fulfill the intent, and derive the form from that understanding, informed by evidence and real constraints.
The user can often recognize what is right or missing before they can articulate it themselves; seeing something specific gives them a way to recognize, correct, or extend the emerging thought. Contribute substantive proposals that help both participants discover and develop what the user is reaching for.
Standalone dialectic begins with the user's explicit request. Within an existing task, another active skill may invoke this method when its guidance calls for it. Keep that use within the task the user requested; its purpose, artifacts, and authorization remain in place. Standalone exploration can end with shared understanding, without requiring an implementation or destination artifact.
Begin with an explicit articulation of the intent: what the user wants to accomplish and what a successful result would make possible. Draw on their words and available context to offer a clear articulation of intent in a blockquote, with enough reasoning to make your interpretation open to examination, and invite correction. Keep the first exchange focused on settling it, and wait for the user to recognize it as right before proposing visions, candidate solutions, or implementation plans. This gives the user a chance to change the question before the proposals narrow its answers.
Carry forward intent already explicitly agreed in the conversation: briefly state it and proceed from that agreement. A request to use dialectic starts this process; it does not itself confirm the agent's interpretation of the intent. Reopen the intent when a correction changes what success means.
At each stage, offer a distinct proposal the user can examine, starting with the first attempt. Once intent is agreed, show what the user needs to examine next: a vision when the direction needs judgment, proposed work when its form needs judgment, or an example of its use when the consequences need to become visible. Connect these contributions when that helps. Put articulations of intent and vision in blockquotes, with explanation and questions outside them, and show other work in the form that lets the user judge it directly. Give enough context for each proposal to be understood on its own, and bold the parts that need particular attention.
Compare possibilities when their differences help clarify what is uncertain: what the user wants to make possible, what vision would fulfill that intent, or how to give that vision concrete form. Make those differences tangible enough for the user to recognize, correct, or develop. Recommend a direction when you have grounds, and explain your judgment.
A single proposal may be enough. Offer further possibilities when they help develop the thought. When a direction is recognized, carry it forward; further comparison should serve a question that remains open.
Develop each proposal through attempts and responses. Keep the proposal and the invitation to respond visibly separate. Choose an invitation that would help the next contribution: an open invitation when the user is discovering what they mean, or a focused question when a specific uncertainty matters. Follow the part they take up rather than requiring a set of answers.
Accumulate the user's phrases, distinctions, examples, and corrections as material for the next proposal. Carry recognized parts forward so the user need not identify them again, preserve selected wording exactly, and compose the next attempt yourself.
Pause for recognition of the intent and the vision before building work that depends on them. Within a recognized direction, develop the work without reconfirming each piece; bring back consequential choices that need the user's judgment. Recognition settles what the user actually examined. Reopen an earlier understanding when a correction changes success or a later discovery changes its premise.
Clarify the intent
Reconsider the framing itself as you form that reading. When the user brings a proposed solution, explore what they want it to accomplish. Use their examples and reactions to examine assumptions about the purpose, scope, or problem being addressed.
Treat a felt mismatch as a substantive starting point. The user may recognize that something feels wrong while struggling to explain why. Use the concrete situation to propose the expectation, relationship, or assumption that might account for their reaction. Develop the model together through their responses; an initial explanation remains a proposal to examine.
When drawing lessons from an experience, distinguish what happened from your explanation of why it helped. Examine the evidence for that explanation before turning it into a general rule.
An example or exploratory proposal may help reveal what the user means. The conversation may clarify a thought the user already held or discover one neither participant had fully formed. Aim for a shared articulation strong enough to guide the vision.
Develop the vision
Starting from the shared intent, imagine the strongest coherent way to fulfill it. Reconsider the relevant whole as if that intent had been understood from the beginning, and explore what becomes possible when existing forms, boundaries, and assumptions are open to change.
Make that vision tangible enough for the user to judge. Show what they would experience, understand, or be able to do through a concrete expression or example of its use. Choose the form that reveals what matters: a passage, conversation, interface, diagram, or rendered preview. Develop it far enough to expose the consequences under discussion.
Aim for a coherent vision specific enough to guide the structure and details.
Work backward into concrete form
Work backward from the shared vision to the structure, decisions, and details needed to realize it. Examine which existing parts support that direction and which need to change.
Develop the work in coherent pieces the user can judge. Choose the scope of each attempt around a consequential question or decision. Show the actual wording, design, interface, or code, with enough context to reveal how it works. When revising, show the current and proposed versions together so the user can examine what changes. Let the vision guide the whole while reviewing pieces at the user's pace.
Carry settled choices into the authorized work. Check facts and behavior you can establish, distinguish illustrative proposals from actual results, and show rendered work when appearance or movement matters. Read or examine the assembled whole against the intent and vision; individual pieces may reveal a problem when brought together.
References
Read the example conversations when calibrating the progression or how to make a proposal judgeable. The complete example shows intent, vision, and concrete form developing through corrections and explicit recognition. Focused excerpts show particular judgments within a stage; their introductions establish the shared understanding they build on. All invented exchanges are illustrations, not measured results or records of the user's preferences.
When the user is authoring prose in their own voice, use their personal
writing-voice skill if one is available. Without it, develop the prose
through this skill and the destination's guidance. Page and journal
workflows retain their authorship and artifact requirements, including the
boundary against inventing personal events, motives, or beliefs.