wrkr

Convert user-provided recommendations into a timestamped, execution-ready backlog plan using the active repo profile. Use when a repo needs a one-off plan that should not overwrite PLAN_NEXT.

Verify implemented Factory plans against original source requirements, run all required validation lanes, create a repair branch when gaps exist, and fix gaps until all requirements are satisfied.

Implement any valid Factory execution plan story-by-story using the active repo profile, planned changelog/versioning fields, and required validation lanes.

Convert repo-owned strategic ideas into a timestamped, execution-ready backlog plan using the active repo profile.

Run a profile-driven evidence-based OSS/product readiness audit across product model, onboarding, architecture, DX, security, release readiness, and market wedge.

Delete non-default local and configured-remote branches one-by-one using the active repo profile, safety checks, and a final prune/report.

Perform a profile-driven full-repository or scoped code review with severity-ranked findings focused on contracts, boundaries, fail-closed safety, determinism, portability, release integrity, and docs correctness.

Commit scoped changes, push a branch, open or update a PR, and keep driving profile-defined CI, passive review, merge, and post-merge loops until success or a hard blocker remains.

Resolve changelog-derived semver, finalize the release changelog through Factory scripts, tag from the default branch, monitor release/UAT, and run bounded hotfix loops when failures are actionable.

Transform the Wrkr PRD in product/wrkr.md into a world-class, zero-ambiguity execution plan that mirrors the detail level of product/PLAN_v1.md (or gait/product/PLAN_v1.md when needed), while enforcing product/dev_guides.md and product/architecture_guides.md standards for coding, testing, CI, determinism, architecture governance, and contracts. Use when the user asks for an initial build plan from the PRD (not from ideas/recommendations).

Pull all comments from user-provided PR numbers, implement fixes, validate, and ship via commit-push. For closed/merged PRs, use follow-up branches from main.