feature-dev

You can automate feature development by providing a user story or issue URL to initialize a pipeline that handles branch and worktree setup, PRD generation, and execution orchestration, resulting in a fully implemented and traceable feature branch.

Plan-first PRD generation enforces a mandatory planning phase before creating Product Requirement Documents, ensuring scope validation and alignment before proceeding with feature development execution and artifact generation.

Yes, you can use GitHub issues to initialize both individual and multi-story pipelines, which automatically generate dedicated worktrees, PRDs, and Ralph configurations while managing branches and ensuring all artifacts are committed and pushed.

Yes, feature development orchestration creates and manages dedicated git worktrees for each pipeline, ensuring branch isolation and scope validation while maintaining artifact traceability across every phase of the development workflow.

When UI changes are detected during feature development, the pipeline ensures agent-browser verification and integrates visual testing hooks to validate UI modifications before artifacts are committed and pushed to the remote repository.

Automated feature development pipelines require a mandatory planning phase before PRD generation and rely on Ralph conversion for execution orchestration, meaning stories lacking clear scope validation or bypassing the planning phase cannot proceed through the workflow.