spec-planning

To generate a feature implementation plan from NFRs and acceptance criteria, provide a feature name along with its NFRs and acceptance scenarios. The skill translates these inputs into an actionable plan.md and eval_criteria.yaml.

A feature plan derived from architecture and evaluation standards includes detailed tasks, components like ports and adapters, test plans, LLM eval hooks, risks, and ADR status considerations to ensure governed implementation.

You create eval_criteria.yaml for software feature evaluation by deriving it from defined NFRs and acceptance criteria. The output includes evaluation thresholds and references to FIRST/Virtues standards to enable governed testing.

Yes, planning feature implementations requires reading inputs from features/<feature_name>/nfrs.md and features/<feature_name>/acceptance.feature. These files scope the feature before generating the execution plan.

The best way to align feature tasks with architecture and evaluation criteria is to translate NFRs and acceptance scenarios into a concrete plan. This ensures all tasks, components, and test plans adhere to architectural standards.

Feature plans need ADR considerations and LLM eval hooks to document architectural decisions and enable governed evaluation. Including these elements ensures the implementation addresses technical risks and meets evaluation thresholds.