behavior-spec-writing

To generate Gherkin behavior specs, the Skill reads your implementation plan from docs/plan and drafts structured feature and core module specifications. It outputs these files under docs/spec/feature-spec/ and docs/spec/core-spec/ for review.

The best way to lint feature-spec files is using gherkin-lint to validate new or updated behavior specifications. This ensures your Gherkin outputs conform to the project's standard format and workflow before they are stored as memory.

Yes, you can draft core-spec files for existing modules. The Skill reads planning documents and produces core specs under docs/spec/core-spec/, ensuring consistent expectations and reusability across different modules in your project.

Yes, a docs/plan directory is required because the Skill reads the implementation plan from that location to produce feature and core specs. Without it, the tool lacks the context needed to draft the Gherkin behavior specifications.

Storing behavior specs as memory preserves system behavior definitions under docs/spec. This knowledge memory guides future implementation and changes by maintaining reusable, linted Gherkin feature and core specs that prevent ambiguity across teams.