Morning Star — Agent Plugin for harness engineering workflows: a TS Harness Workflow Engine (@mstar-harness/engine) that enforces deterministic workflow gates, plus mstar- judgment skills for multi-agent code delivery across OpenCode, Cursor, Codex, Kimi Code, ZCode, and omp.
Instructions for btspoony/mstar-harness, a project described as: An omni-plugin for harness engineering workflows with multi-agents, programmatic gates and skills.
A technical architecture role for designing systems, making technical decisions, and writing technical documents. ADR means a written record of an important architecture decision.
A read-only code reviewer for SDD task reviews and codebase audits. SDD is a way to define and deliver software through structured tasks and design information.
前端开发工程师 - 页面/组件/交互/a11y/前端性能。全栈功能里默认前端主责(与 @fullstack-dev 分轨);纯 UI 任务首选本角色。 Frontend Developer - pages/components/interactions/accessibility/frontend performance. This is the default frontend owner in fullstack work (split with @fullstack-dev) and the preferred role for pure UI tasks.
A second full-stack development role for work that can run alongside another developer’s track. Full-stack work covers both application interfaces and server-side code.
A backend-led full-stack development role for implementing APIs, business logic, data layers, and related frontend work. Full-stack means work that spans both the user interface and server-side systems.
A product-planning role for understanding needs, defining products, researching users and markets, and writing product documents. It focuses on deciding what should be built and why.
A code-review role focused on changes, program logic, and whether the architecture will remain maintainable. It is a reviewer, not a person who runs tests.
A writing-focused subagent for documentation, fiction, copywriting, and scripts. The description says it must first load shared workflow and role instructions before working.
Deep, pre-merge review of a PR / branch / diff at three strengths — quick / default (default) / deep — one verdict, posted to GitHub when a PR number is given. Decides whether a change is safe to ship with evidence-backed findings, rather than a shallow "looks good" pass. Produces a ship it / needs fixes / blocked…
Survey a codebase as a senior advisor and produce prioritized, self-contained improvement plans. Read-only on source code. Use standalone before iteration-start to discover what's worth doing, or independently to build a prioritized backlog.
Drive the active iteration to completion — Phase 2 Autonomous Execute, Phase 3 iteration-close, Phase 4 Create PR, Phase 5 PR merge-ready loop (prefer babysit/-babysit; optional greploop when repo has it; else CI fallback) until mergeable. Not Done until Phase 5 exit checklist passes.
Autonomous full iteration loop for cloud agents — Phase 1 (code-first auto direction lock + compass/plans + Review & Edit chain) through Phase 2–5 (execute → close → PR → merge-ready). Optional args: direction, scale (S|M|L|XL, default M). Not Done until Phase 5 exit checklist passes. Minimal human intervention; no…