Senior Planning Team FAQs

Question 1

What are the primary outputs of the Senior Planning Team skill?

Accepted Answer

The skill produces two core documents: a comprehensive SPEC.md containing technical architecture and UX design, and an IMPLEMENTATION_PLAN.md which provides a step-by-step roadmap for coding the feature.

Question 2

Why is the Security Interview considered mandatory?

Accepted Answer

The skill follows a 'Security by Design' philosophy, ensuring that data protection, authentication, and threat modeling are addressed in the specification phase rather than as an afterthought.

Question 3

Does it always run every interview phase for every task?

Accepted Answer

No, the skill includes a Task Classifier that analyzes your specific request to skip irrelevant phases—such as skipping the UX interview for backend-only infrastructure tasks—to save time.

Question 4

Can this skill adapt to my existing project's coding style?

Accepted Answer

Yes, the workflow includes a Discovery phase and a Code Rule Reader that searches your codebase for AGENTS.md, CLAUDE.md, and other convention files to ensure all plans follow your local standards.

Question 5

How long does the planning process typically take?

Accepted Answer

Depending on the complexity and task classification, the process typically ranges from 65 to 105 minutes of deep analysis, interviewing, and document synthesis.

Senior Planning Team

Key Features

Use Cases

Senior Planning Team

Key Features

Use Cases