intent-translator

Translate vague development intents into ranked implementation options with tradeoffs.

20|3|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/DVNghiem/FlowDeck --skill intent-translator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: intent-translator
Source: https://github.com/DVNghiem/FlowDeck/tree/main/src/skills/intent-translator
Command: npx skills add https://github.com/DVNghiem/FlowDeck --skill intent-translator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Convert vague requests like "make checkout faster" into concrete, ranked implementation options with tradeoffs before coding starts.

Core Features & Use Cases

  • Parses ambiguous goals and surfaces 3–5 concrete approaches with scope, effort, risk, and tradeoffs.
  • Ranks options by impact-to-effort ratio and highlights the best pragmatic path.
  • Enables rapid decision-making and planning before a line of code is written.

Quick Start

Translate a vague request into a ranked menu of concrete implementation options before coding.

Frequently Asked Questions about intent-translator

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

FAQPage Schema
How do I translate a vague development intent into concrete implementation options?

To translate a vague development intent, parse ambiguous goals to surface three to five concrete approaches with scope, effort, risk, and tradeoffs. This generates a ranked menu of implementation options before coding starts.

What is the best way to plan codebase changes for a vague request like making checkout faster?

The best way to plan codebase changes is ranking implementation options from the vague request. This surfaces concrete approaches with affected files, effort, risk, and tradeoffs to enable planning before a line of code is written.

Can I generate tradeoffs and ranking for multiple viable approaches in my project?

Yes, you can generate tradeoffs and ranking for multiple viable approaches in your project. The process parses ambiguous goals to produce up to five options, each detailing files affected, effort, risk, and specific tradeoffs.

Does ranking implementation options work for codebases where multiple viable approaches exist?

Yes, ranking implementation options works for codebases where multiple viable approaches exist. It translates ambiguous development intents into a ranked menu of concrete options with scope, effort, risk, and tradeoffs.

When do I need to generate a ranked menu of implementation options with tradeoffs?

You need to generate a ranked menu of implementation options with tradeoffs when facing vague development intents. This enables rapid decision-making and planning by surfacing concrete approaches with effort, risk, and impact-to-effort ratios before coding.