dev

To orchestrate end-to-end feature development, you can use an automated pipeline that chains sub-skills for exploration, design, PRD creation, implementation, review, and PR submission. This reduces manual handoffs by coordinating the entire workflow deterministically.

Automating PRD creation and implementation notes is best handled through a development workflow pipeline that takes a feature description and generates design options, PRDs, and implementation traces. Intermediate outputs are written to .llm/<feature_name>/ for traceability.

Yes, you can pause the feature development pipeline for user input. The workflow supports interactive design prompts, pausing when making design decisions or PR approvals to enable collaborative human-in-the-loop workflows before proceeding to the next stage.

You generate a ready-to-submit pull request by invoking the pipeline with a feature description. The system orchestrates exploration, implementation, and review, culminating in a finalized PR while writing all intermediate artifacts to a designated directory.

Yes, the automated development workflow relies on chained sub-skills to handle code review and release. It orchestrates these sub-skills sequentially within a defined pipeline to ensure deterministic progression from feature design to final PR creation.

Intermediate artifacts during an automated feature development pipeline are stored in the .llm/<feature_name>/ directory. This ensures full traceability of generated design options, PRDs, and implementation notes throughout the end-to-end workflow.