How is analysis-process different from implementation-process?

It focuses on pre-implementation artifacts (PRD, design/spec) and ensures you understand scope, requirements, and a concrete plan before coding.

What outputs does it generate?

PRD/design/spec documents and a detailed implementation plan with milestones, tasks, dependencies, and acceptance criteria.

When should you move to implementation-process?

When the PRD, design/spec, and plan are agreed upon and signed off by stakeholders, you can proceed to implementation-process for coding.

analysis-process

Scanned

npx machina-cli add skill serpro69/claude-starter-kit/analysis-process --openclaw

Files (1)

SKILL.md

1.3 KB

Task Analysis Process

Goal: Before writing any code, make sure you understand the requirements and have an implementation plan ready.

Ideas and Prototypes

Use this for ideas that are not fully thought out and do not have a fully-formed PRD/design/specification and/or implementation-plan.

For example: I've got an idea I want to talk through with you before we proceed with the implementation.

Your job: Help me turn it into a fully formed design and spec, and eventually an implementation plan.

See idea-process.md.

Existing task-master tasks

For tasks that already exist in task-master.

For example: Let's work on task 6 next.

Your job: Make sure the task is well-documented and you fully understand the requirements and how to implement it. Then implement the task using implementation-process skill.

See existing-task-process.md.

Source

git clone https://github.com/serpro69/claude-starter-kit/blob/master/.github/templates/claude/skills/analysis-process/SKILL.md

View on GitHub

Overview

analysis-process helps you convert a feature idea or set of requirements into a fully formed PRD, design/spec, and implementation plan before coding. It clarifies scope, success criteria, dependencies, and risks, ensuring all stakeholders agree on what to build. Use this in pre-implementation stages to lock down the spec and craft a concrete plan.

How This Skill Works

Start with an idea or existing requirements. The process guides you to produce a PRD, design/spec, and a concrete implementation plan with milestones, tasks, and acceptance criteria. It emphasizes scope, success metrics, dependencies, and risk, ensuring a correct plan before writing code.

When to Use It

When you have a feature idea without a formal spec and need a clear plan.
When you must align stakeholders by defining PRD, design, and success criteria.
When preparing for pre-implementation (idea-to-design) stages to avoid coding in the dark.
When turning an existing task or requirement into a formal plan for implementation.
When dependencies, risks, and milestones must be identified before coding starts.

Quick Start

Step 1: Provide the idea or existing requirement.
Step 2: Draft PRD, design/spec, and success metrics.
Step 3: Build an implementation plan with milestones and tasks.

Best Practices

Capture the problem statement and desired outcomes first.
Define PRD sections: goals, scope, success criteria, and non-functional requirements.
List dependencies, risks, constraints, and acceptance criteria.
Create a phased implementation plan with milestones and concrete tasks.
Review with stakeholders and iterate until consensus is achieved.

Example Use Cases

Idea-to-PRD for a new onboarding flow
Formalizing a mobile app feature request into PRD and plan
Converting an 'add social login' idea into a design/spec and plan
Turning a critical bug fix requiring API changes into a PRD and rollout plan
Refining a data export feature across teams with dependencies

Frequently Asked Questions

Add this skill to your agents