where-will-we-end-up-55words

Convert conversation trajectory into a concrete end-result description under 55 words.

1|2|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/jgwill/dotagents --skill where-will-we-end-up-55words
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: where-will-we-end-up-55words
Source: https://github.com/jgwill/dotagents/tree/main/skills/where-will-we-end-up-55words
Command: npx skills add https://github.com/jgwill/dotagents --skill where-will-we-end-up-55words

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you precisely name the manifested end-result of a working conversation so everyone can align on the trajectory, rather than getting stuck in describing actions without a clear destination.

Core Features & Use Cases

  • Desired-state naming: Produces a forward-facing statement of the end-result’s shape, not the current reality.
  • Tight forecast constraint: Enforces a single-paragraph response of strictly fewer than 55 words to sharpen clarity.
  • Alignment language: Uses advancing-pattern phrasing to make the trajectory visible and concrete for stakeholders.

Quick Start

Use this skill to name the desired-state of your ongoing work within 55 words by telling the AI what outcome you want to manifest and the context driving it.

Frequently Asked Questions about where-will-we-end-up-55words

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I define the desired state outcome for a planning conversation?

Forecasting the desired state involves writing a single forward-facing paragraph under 55 words that names the manifested outcome. This constraint sharpers clarity and forces stakeholders to align on a specific, concrete end-result description rather than abstract activities.

Why does stakeholder communication fail to align on a project trajectory?

Stakeholder communication fails when participants describe actions without naming a clear destination. Using advancing-pattern language to forecast the desired state makes the trajectory visible and concrete, preventing alignment breakdowns caused by vague or unbounded planning discussions.

What is the best way to write an outcome definition for forecasting scenarios?

The best way to write an outcome definition is to enforce a strict 55-word limit within a single paragraph. This tight forecast constraint sharpens clarity by forcing you to name only the forward-facing manifested state, omitting uncounted glyphs and unnecessary process details.

Does the 55-word constraint limit the detail in stakeholder alignment communication?

The 55-word constraint intentionally limits detail to sharpen alignment communication. By restricting the forecast to a single paragraph, it forces participants to distill the desired state into its most concrete advancing-pattern form, eliminating filler and ensuring the shared destination remains highly visible.

When do I need to use advancing-pattern language for outcome definition?

You need advancing-pattern language when an in-progress conversation lacks a shared destination. It converts vague planning trajectories into a concrete, forward-facing description of the manifested artifact, ensuring all stakeholders understand the exact desired state being targeted.