feature-architect

To generate technical specifications from user stories, you can use an orchestration skill that analyzes your input, scans your codebase for context, and outputs structured documentation like BRIEF.md and CONTEXT.json files.

Turning high-level feature requirements into a spec is best handled by orchestrating context gathering and codebase scanning to infer constraints, which then generates a BRIEF.md and invokes downstream generators for the final SPEC.md.

Automate context gathering for feature development by running an orchestration process that analyzes user requirements, scans existing code to identify relevant context, and infers technical constraints automatically.

Yes, you can create technical documentation for simpler features using a quick mode, which streamlines the generation of specifications without the full overhead of deep codebase scanning and extensive constraint inference.

Orchestrating specification generation produces CONTEXT.json and BRIEF.md files initially, and then invokes a downstream generator to create a SPEC.md file along with specific screen documents.

The specification generation process operates as an independent orchestration layer with no listed dependencies, though it invokes a downstream feature-spec-generator to produce the final SPEC.md and screen documents.