dev

Automating end-to-end feature development requires orchestrating a sequence of sub-skills to guide teams through discovery, design, PRD, implementation, review, and PR creation. You initiate this automated workflow by passing a feature description to the starting command.

Orchestration in software development workflows coordinates a chain of specialized sub-skills to move a feature from idea to PR. This process manages artifact generation and surfaces design decisions to the team with minimal manual intervention required across the development lifecycle.

Yes, running automated dev workflows requires a specific set of sub-skills named sequentially from start through PR creation. These components must be present and defined with frontmatter metadata to successfully orchestrate the end-to-end feature development process.

Workflow management handles artifacts by writing progress data to a local .llm directory during feature development. This approach stores design decisions and intermediate outputs locally, ensuring the team can review the orchestrated workflow history and generated documentation.

Yes, you can use this orchestration workflow for team collaboration on PR reviews. The system guides teams through the entire feature development lifecycle, explicitly including the review phase and PR creation, while surfacing key decisions to the entire team.