Loglines: Compress a plan until its customer, change, and result are visible
A strategy requires several pages of context before the reader can identify who it serves, what will change, and why the change matters.
The useful response is not more ceremony. It is a mechanism that can compress a plan until its customer, change, and result are visible.
What the skill produces
The Loglines skill turns supplied context into a one-sentence planning statement supported by evidence, assumptions, and a fuller operating plan. It should expose missing evidence instead of inventing it. The free skill packages this mechanism for explicit use. It does not fetch remote instructions, and the practitioner remains responsible for the facts and final decision.
Run the mechanism
- Name the customer or audience and the problem.
- State the proposed change and the result it should produce.
- Test whether the sentence constrains decisions rather than merely sounding memorable.
The owner should review the output against the original evidence before it is used. Any unresolved assumption stays labeled, with an owner and date when it affects the decision.
Failure check
A logline becomes a slogan when it hides the trade-off, uses abstract nouns, or promises a result the evidence cannot support.
Adoption test
Give the sentence to three informed readers without narration. Ask each to identify the customer, change, and intended result. Revise any field they cannot find.
Keep the skill only if it improves the artifact or decision against that baseline. Revise the playbook when the same failure survives more than one review cycle.
Infographic
