aim-ask-strategy

Analyze READMEs to clarify questions and generate three-tier strategy options.

4|1|Updated Apr 18, 2026
One-click install
npx skills add https://github.com/zccz14/AIM --skill aim-ask-strategy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aim-ask-strategy
Source: https://github.com/zccz14/AIM/tree/main/.agents/skills/aim-ask-strategy
Command: npx skills add https://github.com/zccz14/AIM --skill aim-ask-strategy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill helps teams clarify questions, converge directions, and resolve uncertainties before deciding how to proceed and producing a task spec, especially when key clarifications could change the route.

Core Features & Use Cases

  • Consolidates README anchors and constraints to generate a triage of strategy options (upper, middle, lower).
  • Recommends an initial priority and explains the rationale behind the ordering.
  • Guides targeted clarifications so questions impacting strategy ranking are addressed efficiently.

Quick Start

Read the README related to your question, then select an initial upper/middle/lower strategy and note your initial recommendation.

Frequently Asked Questions about aim-ask-strategy

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

FAQPage Schema
How do I clarify questions and converge direction before writing a task spec?

To converge direction before writing a task spec, analyze the README for constraints, frame the strategic uncertainties, and generate upper, middle, and lower strategy options with an initial priority recommendation.

What is the best way to resolve planning uncertainties that could alter the project route?

The best way to resolve planning uncertainties is by generating a three-tier strategy output that triages options, guiding targeted clarifications to address questions impacting strategy ranking efficiently.

Do I need a README analysis to generate upper middle and lower strategy options?

Yes, README analysis is required to consolidate anchors and constraints, which forms the basis for generating the three-tier strategy options and recommending an initial priority with rationale.

Can I use this strategic framing approach for design and decision-making across repository workstreams?

Yes, you can apply this strategic framing approach to design, planning, and decision-making across repository workstreams where unresolved uncertainties could alter the course of the task specification.

Why does generating a three-tier strategy output help with convergence in decision-making?

Generating a three-tier strategy output helps with convergence by structuring the evaluation of options against README constraints, enabling targeted clarifications and a clear initial recommendation for the task spec.