Repository navigation
Flow epic-process: MP-108, MP-109 - #87
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Epic MP-107 (research: https://draft.yokeloop.com/artifacts/mp-107-ship-whfmcjly) — the process «research → independent plan check → subtasks → /flow → stand acceptance → /ship» as commands. The epic itself is research only and is skipped as a key.
MP-108 — Эпик и приёмка эпика в /flow
/flowexplicitly skips a typed epic (review, has subtasks, no pr.md of this flow) and, in Finish before the PR, runs one epic acceptance on a stand when the epic's research names it; subtask stands and the score format are unchanged.pnpm build0,pnpm verify0lsoutside the stand cwd (stand setup), after the announcement and before any write.MP-109 — Скилл /epic и роль plan-challenger
/epic <KEY>(steps 1–5: research, one review on v1, publish, independent check by the new read-only roleplan-challenger, one question per finding written straight into the decisions table, v2, «Подзадачи» with «Завести и запустить /flow»); PIPELINE «Epics» section and «Approval semantics»; AGENTS.md, README, task role prompt + warmup golden, CHANGELOG.pnpm build0,pnpm verify0Epic acceptance (MP-107)
/epic→ «Завести и запустить /flow» → subtasks with--parent, epic in review before/flow,/flowannounced the order with the epic skipped; nothing written after. Engineer: «Провести до PR».Assembled checks (8db61a0)
mise exec -- pnpm build0;mise exec -- pnpm verify0 (fast 228/0, boundary 67/0, cargo 30/0)🤖 Generated with Claude Code