create-feature

To turn a rough feature idea into a structured GitHub issue, you provide a brief description and the tool investigates your codebase to surface patterns. It then asks clarifying questions to generate a ready-to-create issue with user stories and acceptance criteria.

Documenting technical context for a new feature request involves investigating the codebase to find integration points and relevant patterns. This approach ensures the resulting GitHub issue provides clear implementation guidance alongside user stories and use cases.

Generating user stories and acceptance criteria for software planning requires guided discovery and clarifying questions about your feature idea. This process defines edge cases and produces a structured draft ready for development teams to implement.

Yes, you can use codebase investigation to find integration points before creating a feature issue. The tool automatically surfaces relevant code patterns and technical context, ensuring the generated GitHub issue includes accurate implementation details.

Yes, this feature planning approach works without detailed specifications because it starts with only a brief feature description. It guides discovery by asking clarifying questions to define edge cases and build out the full issue structure.

When creating GitHub issues from rough ideas, the main limitation is dependency on the quality of your clarifying answers. The tool structures the issue based on your input and codebase investigation, so incomplete answers may result in less accurate technical context.