mirror of https://github.com/openprose/prose.git synced 2026-09-19 05:55:05 +08:00

Files

T

Raymond Weitekamp f524eefec9 Add prose write authoring workflow (#86 )

* std: add prose author workflow

* cli: refresh brace-expansion lockfile

* std: tighten prose author planning

* cli: make prose write self-contained

* cli: align harness smoke with bundled bootstrap

* Make prose write interactive in host

---------

Co-authored-by: irl-dan <97565471+irl-dan@users.noreply.github.com>

2026-05-19 00:20:56 -04:00

2.4 KiB

Raw Permalink Blame History

name, kind, subject

name	kind	subject
test-prose-author-launch-readiness	test	prose-author

Test Prose Author Launch Readiness

Fixtures

request: | I want a reusable product launch readiness workflow.

Inputs: feature name, launch date, PR links, analytics dashboard links, support/search keywords, and the PM's launch goals.

Run these checks in parallel:
- engineering review: inspect PR status, test coverage, migration risk, rollback path, and unresolved technical blockers
- quality review: inspect test plan, bug backlog, known flaky tests, accessibility checks, and manual QA gaps
- product review: compare launch goals to telemetry, customer support themes, docs readiness, pricing/packaging impact, and success metrics
Then synthesize a launch readiness memo with risks, blockers, owner assignments, go/no-go recommendation, and follow-up tasks.

Loop with a launch editor until the editor approves the memo or 4 review rounds have happened. Each revision must explicitly address prior editor notes.

If there are blocking risks, return a no-go decision with owners and next review date. If approved and no blockers, return a go decision plus the memo, checklist, and stakeholder summary.

Expects

source_package: prefers folder output because the workflow is reusable and has parallel reviews, synthesis, an approval loop, and conditional decisions
source_package: maps inputs into named requires including feature_name, launch_date, pr_links, analytics_links, support_keywords, and launch_goals
source_package: includes explicit parallel execution for engineering, quality, and product review
source_package: preserves the max 4 review-round bound exactly
source_package: carries prior editor notes into every revision round
source_package: includes editor_review_history so approval is auditable
source_package: returns no-go with owners and next_review_date when blockers remain or approval is exhausted
source_package: returns go only when the editor approves and blockers are absent
lint_report: has status pass and no blocking findings

Expects Not

source_package: converts the go/no-go branch into a single vague report
source_package: loses reviewer history or prior editor notes
source_package: changes the review limit from 4 rounds

2.4 KiB Raw Permalink Blame History

Test Prose Author Launch Readiness

Fixtures

Expects

Expects Not

2.4 KiB

Raw Permalink Blame History