devlyn:feature-spec

To generate a feature specification, the skill reads your product-spec.md, locates the matching behavior by name, and writes a build-ready spec file to your feature-specs directory. It automatically infers platform-appropriate interfaces and data models from repository signals.

A build-ready feature spec translates high-level product behaviors into implementable sections including entities, views, permissions, errors, and integration references. It removes guesswork by documenting specific interfaces inferred from repository signals and platform metadata.

You can document feature interfaces by running the skill against your repository. It scans for matching symbols and detects indicators like TypeScript, Python, Solidity, or Anchor to determine likely interfaces and shape the feature spec accordingly.

Yes, feature spec generation supports TypeScript, Python, Solidity, and Anchor repositories. It scans your codebase for matching symbols and platform indicators to infer the correct UI, API, CLI, or contract interfaces for the generated spec.

Yes, you can generate platform-specific feature sections. The skill infers platform capabilities from meta.platform or repository signals, then includes only the relevant UI, API, CLI, jobs, or contracts sections in the output feature spec document.

Empty interface sections occur if platform metadata is missing and repository signals are unclear. The skill includes relevant sections by inferring platform capabilities from meta.platform or codebase indicators like TypeScript or Python to avoid generating irrelevant sections.