keikaku

Transform vague tasks into phased execution plans with milestones and risk mitigations.

Updated Feb 3, 2026
One-click install
npx skills add https://github.com/hagaji/multi-agent-gineiden --skill keikaku
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: keikaku
Source: https://github.com/hagaji/multi-agent-gineiden/tree/main/skills/keikaku
Command: npx skills add https://github.com/hagaji/multi-agent-gineiden --skill keikaku

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams transform vague tasks into concrete, actionable execution plans.

Core Features & Use Cases

  • Requirements analysis: capture intent, success criteria, constraints, and assumptions.
  • Current-state assessment: gather relevant information, study similar cases, and verify available resources.
  • Strategy formulation: evaluate multiple approaches, compare pros/cons, assess risks, and select the best option.
  • Execution planning: decompose into phases, detail steps, identify dependencies, and set milestones.

Quick Start

Provide a task description and outcomes, and ask the skill to generate a phased execution plan with milestones and risk mitigations.

Frequently Asked Questions about keikaku

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

FAQPage Schema
How do I turn vague project requirements into a concrete execution plan?

To turn vague project requirements into an execution plan, you capture intent, success criteria, constraints, and assumptions, then decompose the work into phased milestones with detailed steps and dependency mapping.

What is the best way to assess risks when formulating a project strategy?

Assessing risks during strategy formulation involves evaluating multiple approaches, comparing their pros and cons, and mapping dependencies to select the best option for your project execution.

How do I map dependencies and set milestones for complex feature development?

Mapping dependencies and setting milestones for feature development requires decomposing the strategy into phases, detailing actionable steps, and defining measurable success criteria for each milestone.

Can I use this approach for multi-path decision scenarios and complex analysis?

Yes, this planning approach applies directly to multi-path decision scenarios and complex analysis by enforcing explicit requirements capture, strategy formulation, and milestone-driven delivery.

What information do I need to provide to generate a phased execution plan?

To generate a phased execution plan, you provide a task description and expected outcomes, which the system uses to produce phases, milestones, and risk mitigations.

When should I not use a milestone-driven planning approach for project management?

You should avoid milestone-driven planning when a task lacks explicit requirements or when current-state resources cannot be verified, as the approach depends on measurable success criteria and dependency mapping.