Structured Project Planning FAQs

Question 1

What does the 'seed' status mean for a plan?

Accepted Answer

A 'seed' status indicates a plan file that contains raw context, notes, or brain dumps. This skill uses those seeds to automatically draft organized phases and actions.

Question 2

Why does the plan need to be updated after every action?

Accepted Answer

Since chat history is ephemeral, updating the plan file after every commit ensures that the current state of the project, including decisions and observations, is saved permanently for future AI sessions.

Question 3

What is a persistent plan file in Eidos?

Accepted Answer

A persistent plan file is a structured markdown document stored in your repository that records the phases, atomic actions, and status of a complex task, ensuring Claude maintains context across different work sessions.

Question 4

How does this skill help with architectural alignment?

Accepted Answer

The skill checks for existing design specifications before creating a plan. If no spec exists, it prompts the user to create one, ensuring that implementation steps always follow a documented design.

Question 5

Can I use this for simple bug fixes?

Accepted Answer

While intended for multi-step work, it can be used for any task. However, it is most valuable for procedural work like migrations, cleanups, or new features where the order of operations and verification are critical.

Structured Project Planning

Structured Project Planning

Key Features

Use Cases

Key Features

Use Cases