Run any Skill in Manus with one click

ask-light

Stars4

Forks1

UpdatedJuly 1, 2026 at 07:09

Fast, low-friction planning interview for vague product, web page, app, education content, feature, or implementation requests. Use when the user wants a quick plan before building, wants only a few clarifying questions, or asks for a lightweight "ask before build" pass.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

kakio426

kakio426/ask-me-plan

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Project Management SpecialistsBusiness and Financial Operations Occupations·SOC 13-1082

File Explorer

2 files

SKILL.md

readonly

name	ask-light
description	Fast, low-friction planning interview for vague product, web page, app, education content, feature, or implementation requests. Use when the user wants a quick plan before building, wants only a few clarifying questions, or asks for a lightweight "ask before build" pass.

Ask Light

Overview

Use this skill to turn a vague request into a small, implementation-ready brief with minimal friction. Ask in the user's language.

Interview Rules

Ask 3-5 essential questions total.
Ask one compact round first; use one follow-up round only when the answer is ambiguous.
Keep questions concrete, answerable, and tied to the next implementation step.
Separate confirmed facts from assumptions.
Stop asking when the user says to proceed, stop, build, or that the plan is enough.

Opt-Out

If the user explicitly declines questions (for example: "no questions, just build", "skip the interview"), first check whether the request is concrete enough to guess safely.

If the goal, primary user, and first-version scope are already clear enough from context, skip the question set: state your best-guess assumptions for goal, users, first-version scope, and constraints as a short list, mark them clearly as assumptions rather than confirmed decisions, and go straight to Output.
If even one of those is unclear enough that a wrong guess would produce a fundamentally different result, ask exactly one question to resolve that single biggest unknown, then proceed without further questions.

Question Set

Ask the smallest useful subset:

What should the finished thing help the user accomplish?
Who is the primary user or audience?
What must be included in the first version?
What should be excluded or avoided?
Are there style, platform, deadline, data, or technology constraints?

If the request is visual, route to ask-visual before finalizing. If the request is education-related, route to ask-educator when one or two extra education questions would prevent rework.

Output

Use these section names so later Ask skills (and the user) can pick up the state without re-deriving it:

Confirmed Decisions
Assumptions
Open Questions (omit if none remain)
Non-Goals
Implementation Prompt

Keep the implementation prompt short enough for direct handoff to a coding agent.

More from this repository

same repository

ask-prompt

kakio426/ask-me-plan

Convert an Ask planning interview, notes, product brief, or clarified idea into an implementation-ready prompt for Codex or another coding agent. Use after ask-light, ask-standard, ask-deep, ask-visual, ask-educator, or ask-risk when the user needs a precise handoff prompt.

2026-07-084

ask-risk

kakio426/ask-me-plan

Planning risk interview for finding assumptions, contradictions, missing requirements, privacy issues, UX gaps, education-specific gaps, and implementation ambiguity before building. Use when a plan feels underspecified or when rework would be costly.

2026-07-084

ask-deep

kakio426/ask-me-plan

Detailed, multi-round planning interview for complex services, apps, websites, education products, AI workflows, or ambiguous projects where premature implementation would create rework. Use when the user wants many questions, deep clarification, or a full planning pass before implementation.

2026-07-014

ask-plan

kakio426/ask-me-plan

Entry point for the Ask Me Plan skill suite. Use when the user wants to plan something before building but has not said how deep the interview should be, or is not sure which Ask skill fits (quick, standard, deep, visual, education, risk, prompt, or build).

2026-07-014

ask-standard

kakio426/ask-me-plan

Balanced planning interview for service planning, web pages, apps, education content, product features, and implementation work. Use when the user wants the agent to ask clarifying questions before building and produce a practical implementation prompt.

2026-07-014

ask-build

kakio426/ask-me-plan

Start implementation from an approved Ask planning prompt. Use after ask-prompt or a completed Ask planning interview when the user has a concrete plan and wants Codex to build, preferably with builder, reviewer, and QA subagents when multi-agent tools are available.

2026-07-014

name	ask-light
description	Fast, low-friction planning interview for vague product, web page, app, education content, feature, or implementation requests. Use when the user wants a quick plan before building, wants only a few clarifying questions, or asks for a lightweight "ask before build" pass.

Ask Light

Overview

Use this skill to turn a vague request into a small, implementation-ready brief with minimal friction. Ask in the user's language.

Interview Rules

Ask 3-5 essential questions total.
Ask one compact round first; use one follow-up round only when the answer is ambiguous.
Keep questions concrete, answerable, and tied to the next implementation step.
Separate confirmed facts from assumptions.
Stop asking when the user says to proceed, stop, build, or that the plan is enough.

Opt-Out

If the user explicitly declines questions (for example: "no questions, just build", "skip the interview"), first check whether the request is concrete enough to guess safely.

If the goal, primary user, and first-version scope are already clear enough from context, skip the question set: state your best-guess assumptions for goal, users, first-version scope, and constraints as a short list, mark them clearly as assumptions rather than confirmed decisions, and go straight to Output.
If even one of those is unclear enough that a wrong guess would produce a fundamentally different result, ask exactly one question to resolve that single biggest unknown, then proceed without further questions.

Question Set

Ask the smallest useful subset:

What should the finished thing help the user accomplish?
Who is the primary user or audience?
What must be included in the first version?
What should be excluded or avoided?
Are there style, platform, deadline, data, or technology constraints?

If the request is visual, route to ask-visual before finalizing. If the request is education-related, route to ask-educator when one or two extra education questions would prevent rework.

Output

Use these section names so later Ask skills (and the user) can pick up the state without re-deriving it:

Confirmed Decisions
Assumptions
Open Questions (omit if none remain)
Non-Goals
Implementation Prompt

Keep the implementation prompt short enough for direct handoff to a coding agent.