engineering-workflow
v0.1.0+codex.20260918204832通用工程工作流:从 ask-matt 路由需求澄清、Spec、设计审查、Ticket、TDD 实现到 PR 交付和合并后清理。
By Local Workflow MaintainerLicense: Proprietary0 GitHub starsUpdated 4 days ago
Directory evidence
- Runtimes
- Codex
- Parsed components
- 10 skill or MCP entries
- Source updated
- Sep 19, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install engineering-workflow for Codex
codex plugin marketplace add K999999999999/agent-plugins
codex plugin marketplace upgrade personal
codex plugin add engineering-workflow@personalPaste and run these commands in a terminal with Codex. They add and refresh the personal catalog, then install this plugin.
Compatibility: the page URL and API slug “engineering-workflow” remain stable.
- Codex:
engineering-workflow@agent-plugin-marketplace→engineering-workflow@personal
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/K999999999999/agent-pluginsClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/engineering-workflow/.
Plugin files
├── .codex-plugin/plugin.json├── skills/ask-matt/SKILL.md├── skills/workflow-code-review/SKILL.md├── skills/workflow-delivery/SKILL.md├── skills/workflow-design-review/SKILL.md├── skills/workflow-grill-with-docs/SKILL.md├── skills/workflow-implement/SKILL.md├── skills/workflow-tdd/SKILL.md├── skills/workflow-ticket-readiness/SKILL.md├── skills/workflow-to-spec/SKILL.md└── skills/workflow-to-tickets/SKILL.md
Included Skills10
显式启动通用工程工作流,按需求阶段、软件生命周期、变更大小和风险路由到 Spec、Design Review、Ticket、TDD、Review 或 PR 交付。
在当前上下文只读检查实现是否满足 Spec 或 Ticket,并审查变更的正确性、可理解性、持续可维护性、测试证据和受影响工程边界。
将已形成 candidate 的变更按目标仓库规则完成风险匹配的最终验收、CI 反馈、PR、Auto-merge 监控和合并后清理。
在编码前只读审查已确认的 Spec 或实现设计,重点验证 Use Case、变化边界、依赖方向、复杂度、Contract、可测试性和最小充分设计。
在工程任务的目标、术语、事实源、范围或设计尚不清楚时,通过一次一个问题完成需求澄清。
根据已确认的 Spec、Ticket 或明确的小范围任务,在 Contract 内完成可靠、可测试、职责清晰且最小充分的实现、Review 和本地 Commit。
使用 Red-Green-Refactor 为目标项目的 Contract、行为、边界和失败行为建立可维护、确定性且与风险匹配的测试证据。
在 Ticket 正式写入和用户确认前,只读检查 Scope、变更形状、依赖、Owner、验收、迁移 / 回滚、验证证据和实施边界。
把已经澄清的需求和仓库事实整理为可确认的行为 Spec,明确行为、生命周期、事实来源、取舍和验证,不重新访谈或擅自改变项目规则。
把已确认且通过设计审查的 Spec 拆分为可独立验证、可审查、可回滚或可迁移的纵向 Ticket。
Plugin manifests1
{
"name": "engineering-workflow",
"version": "0.1.0+codex.20260918204832",
"description": "通用工程工作流:从 ask-matt 路由需求澄清、Spec、设计审查、Ticket、TDD 实现到 PR 交付和合并后清理。",
"author": {
"name": "Local Workflow Maintainer"
},
"license": "Proprietary",
"skills": "./skills/",
"interface": {
"displayName": "Engineering Workflow",
"shortDescription": "从需求澄清到实现、Review 和 PR 交付",
"longDescription": "通用工程工作流插件:读取目标仓库规则,从需求澄清、Spec、设计审查、Ticket、TDD 实现和 Clean Code Review 一直到 PR、Auto-merge 监控与合并后清理。",
"developerName": "Local Workflow Maintainer",
"category": "Developer Tools",
"capabilities": [
"Interactive",
"Write"
],
"defaultPrompt": [
"$ask-matt 评估当前工程任务并路由到合适阶段"
]
}
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[engineering-workflow on Agent Plugins Marketplace](https://pluginsmp.com/plugins/engineering-workflow)