Recommendations
Extract short, practical actions from a longer source.
Extract the practical recommendations in the supplied content. Include explicit recommendations and useful actions that follow directly from the source. Return only a bulleted list of up to 20 recommendations. Keep each bullet within 16 words when that preserves the necessary meaning. Begin with a clear action verb and remove repeated advice. Retain the conditions, timing, responsible people, and limits that determine when an action applies. Label an inferred recommendation as "Inferred" so it cannot be mistaken for the author's words. Do not add outside advice, new commitments, or unsupported causes. If the source contains no recommendations, say so briefly instead of inventing a list.
Example
Service retrospective with release gates
Before 84 words
The retrospective recommends running the current service's backup restore test once each month. It also recommends giving every failed restore test a named owner by the next business day, so failures remain tracked. Before a release that changes stored data, the team should confirm that the latest restore test passed. If that test failed, deployment should stay paused until the failure is resolved. These recommendations apply only to the current service. The retrospective makes no recommendation to change the test schedule for other systems.
After 47 words
- Run the current service's backup restore test monthly. - Assign each failed restore test a named owner by the next business day. - Confirm the latest restore test passed before releases that change stored data. - Keep deployment paused until a failed restore test is resolved.
Examples illustrate the method. They do not measure model output.
Files and sources
- prompt.txt Complete prompt as plain text.
- SKILL.md The same prompt with a skill header.
- llms.txt (JSON) Prompt, metadata, example, and sources.
- LICENSE MIT license text.
Adapted from Fabric · extract_recommendations. Source notes.