moooon
Motir
Vibe the project. Bring an idea — Motir's three AI layers plan it, track it, and ship it, end to end. You're looking at Motir, built in Motir.
- Vibe Project
- Open Source
- AI Agent
- AI Loop
- 5
- 요청
- 4
- 추천
- 462
- 계획됨
- 4,328
- 출시됨
- Planning bug: MOTIR-3371 turned "toHaveLength(1) passed, SO a second window opened" into an acceptance criterion — a second mechanism produces that presentation and reproduces 2 in 10
- Planning bug: the MID-SENTENCE WIDENING sweep is owed AGAIN — three packs red for the third time, so MOTIR-2966's remedy collects the debt without stopping it accruing
- Planning bug: an acceptance criterion demanded evidence from a substrate on the OTHER side of a service boundary — "asserted against a real database" for an HTTP seam
- Planning bug: a story scoped its population from where a corpus "STOPS" — but the coverage was a SET, not a prefix, so 44 entries below the boundary were invisible to every check
- Planning bug: a card forbade the only layer at which its own acceptance criterion was implementable — a prescribed layer is a CLAIM about that layer, and it owes the ADR check
- Planning bug: a test card's fixture table encoded axis semantics that contradict the three-axes-are-independent rule its own parent story states in prose
- Planning rule: NEVER reopen a `done` work item — plan forward, and log a bug or a new story instead
- Planning bug: guard #4 says an advisory's reference is "a `blocked_by` to WIRE" — followed literally on a CROSS-STORY reference it produces a cross-parent edge, which gate 7 forbids
- Planning bug: `_shared.md` says "Epic is not an offered kind" — the MCP has offered it all along, so every pass routes around a tool that works
- A story whose deliverable was a PAGE planned no instrument that OPENS it until its last card — a client-boundary 500 lived through five green subtask PRs
- Planning bug: MOTIR-2853 read `ready: true` with two unexecutable preconditions — an external credential and a post-deployment soak window, neither expressible as an edge
- Planning bug: MOTIR-3249 gates four children behind a POST-DEPLOY measurement, so the story cannot be run as a parent
- Planning bug: two MOTIR-3249 children were pinned to ONE repo while their criteria need the other
- Planning bug: MOTIR-3229 names THREE homes and assigns home 2 to MOTIR-3203, which closed without it — `run.md`'s parent-run still stops only on a `design`/`manual` stopper
- Planning bug: an acceptance criterion named TWO triggers for one event-driven seam, and one of them is a non-terminating loop — the card's own explanation names only the other
- Planning bug: a grep-shaped acceptance criterion whose PATTERN also appears in the comments FORBIDDING it is unfalsifiable — MOTIR-3226's AC 7 returned 3 hits on `origin/main` at authoring time
- Planning bug: a card's own detection query prescribed `gh pr view --json files`, which caps at 100 — and the cap became a finding in the card's evidence table
- Planning bug: a contrast ratio was measured in ONE theme context and generalised to "light" — `data-palette` makes it twenty, and four of them failed
- Planning bug: `run.md` never says the at-scale lane is LABEL-gated, so a run labels the PR AFTER creating it — a second trigger at the same sha whose cancelled run poisons the card's CI verdict
- Planning bug: a design card specified a CONSTRUCTION (a true normal-offset band) without checking it was geometrically possible at the mark's own proportions