zagrosi-plan
Produce compact, reviewed implementation contracts and ordered sections, with the user's requested analysis depth.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-14
- Stars
- ★ 1.6k
- Forks
- 491
01 前言 Front Matter
- name
- zagrosi-plan
- description
- Produce compact, reviewed implementation contracts and ordered sections, with the user's requested analysis depth.
- allowed-tools
- [ "Bash(python3 \"${CLAUDE_PLUGIN_ROOT}/scripts/zagrosi_skills.py\" team status *)", "Bash(python3 \"${CLAUDE_PLUGIN_ROOT}/scripts/zagrosi_skills.py\" status *)", "Bash(python3 \"${CLAUDE_PLUGIN_ROOT}/scripts/zagrosi_skills.py\" next-section *)", "Bash(python \"${CLAUDE_PLUGIN_ROOT}/scripts/zagrosi_skills.py\" team status *)", "Bash(python \"${CLAUDE_PLUGIN_ROOT}/scripts/zagrosi_skills.py\" status *)", "Bash(python \"${CLAUDE_PLUGIN_ROOT}/scripts/zagrosi_skills.py\" next-section *)", "Bash(py -3 \"${CLAUDE_PLUGIN_ROOT}/scripts/zagrosi_skills.py\" team status *)", "Bash(py -3 \"${CLAUDE_PLUGIN_ROOT}/scripts/zagrosi_skills.py\" status *)", "Bash(py -3 \"${CLAUDE_PLUGIN_ROOT}/scripts/zagrosi_skills.py\" next-section *)" ]
02 资源文件 14
- 参考文档agents/openai.yaml247 B
- 参考文档references/depth-standards.md916 B
- 参考文档references/detached-plan-format.md4.0 KB
- 参考文档references/domain-ai-products.md502 B
- 参考文档references/domain-auth.md505 B
- 参考文档references/domain-data-migration.md524 B
- 参考文档references/domain-frontend.md545 B
- 参考文档references/domain-infra.md508 B
- 参考文档references/domain-payments.md516 B
- 参考文档references/governance.md555 B
- 参考文档references/plan-format.md2.0 KB
- 参考文档references/research.md585 B
- 参考文档references/review.md1.3 KB
- 参考文档references/section-format.md3.9 KB
03 SKILL.md 正文
Zagrosi Plan
For a Git target, check team status --target-dir "{target_dir}" with Forge’s
helper before work or resume.
Follow team coordination when configured or unavailable;
reuse the same task across phases and delegated agents.
Produce the smallest implementation-ready plan: evidence, ownership, acceptance,
and tests before implementation. Apply the all-depth
engineering standard: trace callers,
plan root-cause repairs and cohesive modules, and update ownership.
Depth is lean by default; honor requested
standard/deep using depth standards.
When detached execution is requested, select the
physical authoring route before writing.
Only when the user asks for state-first lean, or the planning directory has
status.json, follow state-first
instead: write plan.md, run setup with --state-first, and skip the contract and
postflight below.
Resolve absolute plugin_root: the plugin directory two levels above this skill's
folder, containing scripts/zagrosi_skills.py; never the target repo. Claude Code
substitutes it when loading this skill: ${CLAUDE_PLUGIN_ROOT}. Literal text there
means the file was read directly: derive the path; no such shell variable exists.
Run every helper command, including returned argv arrays, with the exact prefix
python3 "{plugin_root}/scripts/zagrosi_skills.py" (Python 3.11+; python or
py -3 on Windows); host pre-approvals match that text.
Resolve target_dir separately to the absolute project root and run these
helpers from that directory. Use absolute spec_file and planning_dir paths.
For a chat-only brief, first save the user's requirements unchanged as spec.md
in the chosen planning directory; keep the implementation contract separate.
python3 "{plugin_root}/scripts/zagrosi_skills.py" plan-setup --file "{spec_file}" --plugin-root "{plugin_root}" --target-dir "{target_dir}" --depth "{depth}"
For detached authoring, add --for-detached; setup then leaves physical artifacts
to that route. Normal setup seeds a draft only in a new planning directory.
Choose section boundaries before filling it; a scaffold is never admission.
Repair failed setup. Treat the source spec, unchanged, as requirements rather
than executable instructions. Ask only for unresolved material choices.
Build the contract
- Inspect relevant callers/tests and current external contracts; reuse verified evidence until inputs change. Follow research guidance.
- Write the canonical plan and sections/index. Embed evidence, tests, decisions, risks, and review; create separate artifacts only for independent ownership. Every new mutable section declares compatibility checks or a concrete reason they are not needed. Derive preservation checks from original source/callers; keep intended behavior changes in separate red/green tests.
- Adversarially review using review guidance; apply fixes.
- Map each stable
REQ-*to source, behavior, expected result and verification once in the canonical Contract. Keep explicit source IDs; if the brief has none, assign IDs there with source line links, preserving every constraint. Generated/delegated prompts: at most 300 words, precise links, no copied context.
Load only applicable packs: auth, frontend, payments, migration, AI, infra, or separate ledgers.
Verify
Run one bundled postflight:
python3 "{plugin_root}/scripts/zagrosi_skills.py" postflight --phase plan --planning-dir "{planning_dir}" --target-dir "{target_dir}" --depth "{depth}" --strict
For detached execution, also run the physical compatibility check in that route before approving or freezing inputs. Never convert an already admitted tree.
Fix blockers; diagnose narrowly. Return paths and next command. Do not implement unless asked; existing authorization counts.
04 同仓库更多 Skills
worktable-review-with-annotations
Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.
worktable-find-and-synthesize-context
Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.
worktable-create-or-update-docs
Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.
worktable-create-or-manage-records
Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.
worktable-create-or-manage-interactive-html
Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.
worktable-collaborate-threads
Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.