跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
搜索与研究

engineering-workflow

Required Matt Pocock workflow entry for engineering research, planning, building, debugging and review when Matt is the selected methodology. Track ordered phases, coordinate authorized workers and require evidence. Matt owns engineering in every harness.

romiluz13 · 已有静态检查记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add romiluz13/mifal --skill engineering-workflow

技能说明


name: engineering-workflow description: Required Matt Pocock workflow entry for engineering research, planning, building, debugging and review when Matt is the selected methodology. Track ordered phases, coordinate authorized workers and require evidence. Matt owns engineering in every harness.

Engineering workflow

This is Mifal's execution contract for Matt Pocock's methodology, not an upstream Matt skill. Ask Matt supplies the route map; this adapter makes execution ordered and visible. Use it on every engineering request owned by Matt, including small fixes, research, plans and reviews.

Select the owner

Matt owns engineering in every harness.

Required entry

  1. Read repository instructions and the existing task state. Declare the deliverable, authorized actions, acceptance criteria and one route: research, plan, build, debug or review.
  2. Load the ask-matt skill completely, as step 4 loads a skill (fallback ~/.agents/skills/ask-matt/SKILL.md). Use its current map to select the procedure for the active phase. Do not copy the provider's route graph into harness rules. Before coordinating multiple workers, load the team-lead skill completely the same way (fallback ~/.agents/skills/team-lead/SKILL.md) and select its applicable references. Use Team Lead for explicit team requests, or for consequential coordination with independent tasks when delegation is already authorized. A bounded worker follows its brief's phase; it does not restart the parent lifecycle or recruit more workers outside its recursion envelope.
  3. Before the first edit or dispatch, create or reconcile the route's ordered phase checklist in the existing task state. Read phase record and checks, keep one tracker, and record the active procedure, reads, evidence and applicability decisions there. Preserve the original required outcomes as named Done means; acceptance must reconcile them, not only dispatched tasks. A short request can keep its checklist in the conversation; declare that the file checker was not run. Existing valid research/plans can satisfy a gate after checking them against the current request.
  4. Load the selected skill completely before performing its phase. Prefer the native skill tool; otherwise resolve ~/.agents/skills/<name>/SKILL.md and read it through the filesystem tool. Treat a provider's "call the Skill tool" as this loading operation, one skill per call. Never announce a skill as loaded after reading only its description. Bind its read record to the body hash; a changed body requires a reload, not reuse of an older session read. At entry and material scope/technology changes, use the existing stewardship inventory to discover applicable specialists as well as the phase procedure. Inspect descriptions and scopes, narrow candidates with who, and load only selected bodies. Record consequential omissions in the existing plan or brief prose. A solo agent uses the same selection; no team or new tracker is required.
  5. Show Owner: Matt | Route: <route> | Phase: <phase> | Next gate: <evidence> at entry, consequential transitions and resume. Run the phase-record check (workflow <state> --gate entry|review|accept, and brief <brief> --matt for each brief) before every dispatch, every review and every acceptance, and log each pass first as Check: start <step> | passed | <evidence> at:<UTC>, a new one as each step begins (Check: start to-spec included, when you run to-spec yourself after the griller closes). <step> is a name from the workflow map's Required steps (scope, grilling, to-spec, to-tickets, implement, review, retro), or the route's phase word where the route has no such step; an unknown name (start entry) is refused. A dispatch with no passing Check above it never ran its gate. Continue automatically within authorization; a failed required check holds that gate. Record the passing check and identity, not only the status line.

Ordered phases and completion gates

RouteRequired phase orderEvidence required
ResearchScope/questions → source plan → investigate → synthesize → review claims → verify/reportAnswered questions, dated primary sources, contradictions and uncertainty; every material conclusion checked against evidence. Use Matt's research procedure for delegated investigation when supported and authorized.
PlanScope → inspect code/versioned docs → resolve design decisions → plan → review → verify/deliverAcceptance criteria, affected seams, dependencies, chosen approach, relevant check commands and no unresolved blocking decisions. Use Matt's planning branch where intent or design is unsettled.
BuildScope → research/context → plan → implement → review/remediate → verify final revision → retro → reportObservable success before edits, behavioral slices where applicable, reviewed final diff, passing relevant checks and Matt's session retrospective. Load implement/TDD for behavioral code and code-review at completion.
DebugScope → reproduce/research → hypothesis and fix plan → diagnose/fix → review → regression/final verification → retro → reportObserved original failure, tested root-cause hypothesis, fix removes that failure, regressions pass and the fix receives a session retrospective. Load diagnosing-bugs for diagnosis; every behavioural fix also loads tdd (reusing an existing failing test counts) and code-review before review, while diagnosis-only work does not need tdd. Missing reproduction stays explicit; diagnosis-only work records that no fix was made.
ReviewFix base/scope → inspect context/spec → review → substantiate findings → verify/reportLoad code-review; each finding has a location, trigger, consequence and evidence. Check for duplicates and false positives. Zero findings is valid.

Every request runs its route's full phase sequence by default, one phase at a time, each with its procedu

阅读完整来源 ↗