spec-workflow

Determine the next spec workflow command for a Flutter feature slice.

2|Updated Aug 13, 2023

Search Tags:#feature specs #architecture review #flutter #slice planning #spec workflow #command dispatch

Ready to run

npx skills add https://github.com/NNPopov/movie-theater-tickets --skill spec-workflow-nnpopov

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec-workflow
Source: https://github.com/NNPopov/movie-theater-tickets/tree/main/src/clients/.claude/skills/spec-workflow
Command: npx skills add https://github.com/NNPopov/movie-theater-tickets --skill spec-workflow-nnpopov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes uncertainty when working on a feature slice spec by telling you exactly which spec step comes next, based on the slice's current state and the project's architecture guidance.

Core Features & Use Cases

Spec State Detection: Checks whether a slice has a PRD, plan, requirements, or validation file and maps that to the next required command.
Architecture-Aware Guidance: Reads the project's core architecture and workflow references before advising, so recommendations stay consistent with the repository's conventions.
Use Case: If you are starting a new feature, continuing an in-progress slice, or unsure whether to write a PRD or plan next, this Skill tells you the correct next action without guessing.

Quick Start

Use the spec-workflow skill to tell me which spec command I should run next for the feature slice I am working on.

Frequently Asked Questions about spec-workflow

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

FAQPage Schema

How do I determine the next spec workflow step for a Flutter feature slice?▼

To determine the next spec workflow step for a Flutter feature slice, this Skill inspects the slice folder for existing PRD, plan, requirements, or validation files and maps the current state to the required command.

What is the best way to continue an in-progress feature spec without guessing the next action?▼

The best way to continue an in-progress feature spec without guessing is to analyze the slice's existing spec files and compare analogous slices, which directly advises the correct next command to execute.

Does this spec workflow guidance require reading project architecture references?▼

Yes, this spec workflow guidance requires reading project architecture references and workflow documentation before advising the next action, ensuring recommendations stay consistent with the repository's conventions.

When should I use a spec workflow command dispatcher for feature slice planning?▼

You should use a spec workflow command dispatcher for feature slice planning when starting a new feature, resuming spec work, or unsure whether to write a PRD or create a plan next.

Can I apply this spec state detection to feature slices without existing PRD or plan files?▼

Yes, you can apply this spec state detection to feature slices without existing PRD or plan files, as it maps the empty initial state to the correct starting command for your spec workflow.

Why does command dispatch for feature specs need to inspect analogous slices before advising the next step?▼

Command dispatch for feature specs inspects analogous slices before advising the next step to ensure the generated PRD, plan, requirements, and validation states align with established repository patterns.