refine-outcomes

Name: refine-outcomes
Rating: 5 (50 reviews)
Author: DheerG

Produtividade

Author: DheerG

Reframes implementation descriptions into outcome statements. Invoked by launch commands during outcome refinement.

50stars

Updated 21 days ago

View on GitHub ↗License: MIT

How to add

/plugin marketplace add DheerG/swarms

The exact command may vary by repository. Check the README on GitHub.

For the skill author

Drop this on your repo README

Shows your skill is listed on Skillteca, generates a backlink and trackable traffic.

[![Listada na Skillteca](https://www.skillteca.com.br/api/badge/refine-outcomes/svg)](https://www.skillteca.com.br/skills/refine-outcomes?utm_source=badge&utm_medium=readme&utm_campaign=badge)

Related skills

See all in Produtividade →

Fabric

42.1k

Fabric is an open-source framework for augmenting humans using AI. It provides a modular system for solving specific problems using a crowdsourced set of AI prompts that can be used anywhere.

Produtividadeby danielmiessler

task-intelligence

39.2k

Protocolo de Inteligência Pré-Tarefa — ativa TODOS os agentes relevantes do ecossistema ANTES de executar qualquer tarefa solicitada pelo usuário.

Produtividade#github#gitby sickn33

task-intelligence

39.2k

Pre-Task Intelligence Protocol — activates ALL relevant ecosystem agents BEFORE executing any user-requested task.

Produtividade#github#gitby sickn33

task-intelligence

39.2k

Protocolo de Inteligência Pré-Tarefa — ativa TODOS os agentes relevantes do ecossistema ANTES de executar qualquer tarefa solicitada pelo usuário.

Produtividade#github#gitby sickn33

Category alert

Get new Produtividade skills every Monday

One short email with only the new Produtividade skills. 4 minutes of reading, no spam, unsubscribe with one click.

You confirm your email on the first send. No spam. Unsubscribe with one click.

The user has described what they want. Check if they've stated outcomes or implementations.

An outcome says what changes for the user or business. An implementation says what to build. If they wrote implementations, help them restate as outcomes. If they wrote outcomes, confirm them and move on.

Keep outcomes short — one or two lines each, in plain language. Do not add technical detail, metrics, or architecture. Do not make outcomes longer or more formal than what the user wrote. Simplify, never elaborate.

ShareX LinkedIn

Comments · No comments

No comments yet. Be the first.