start-feature

To generate a feature specification from inline context, provide the feature name, scope, and constraints directly. The skill creates a specification document under docs/workflow/specification/ and delegates finalization to the technical-specification skill.

Skipping formal discussion docs to start a feature spec requires providing concise inline context. This skill validates a proposed topic name, checks for file conflicts, and invokes the technical-specification skill to complete the document.

Inline context for feature design is needed when a feature is already understood and prior discussion is unnecessary. It allows teams to maintain momentum by directly creating a specification file without drafting formal discussion documents.

Yes, the feature specification workflow validates the proposed topic name and checks for naming conflicts under the docs/workflow/specification directory before proceeding with document creation and technical specification handoff.

You can use this skill for standalone feature planning when the scope is known and prior discussion is unnecessary. It directly creates the specification markdown file and coordinates finalization with the technical-specification skill.

A limitation of generating a specification from inline context is that it skips formal discussion documentation entirely. It is unsuitable for features requiring extensive collaborative scoping or unresolved technical constraints before specification.