mawf-brainstorm
Clarify requirements and maintain native MAWF plans, engineering contracts, glossary and ADRs without a task-framework runtime.
- License 许可
- MIT
- 最近更新
- 2026-11-09
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- mawf-brainstorm
- description
- Clarify requirements and maintain native MAWF plans, engineering contracts, glossary and ADRs without a task-framework runtime.
03 SKILL.md 正文
MAWF brainstorm
Use in native MAWF workspaces (.mawf/workspace.json has version: 1,
backend: mawf, trellis: false). Read the workspace AGENTS.md and applicable
docs/engineering/specs/ contracts before design or implementation.
Reuse the existing task under docs/plans/<id>/ when continuing work. Preserve
its task ID, PRD, design, research, and context references. Create a new plan only
when needed and authorized; no framework command is required. Completed task
history lives under docs/history/tasks/.
Use the vendored grilling / grill-with-docs interview method to clarify unresolved requirements. Inspect repository facts yourself. Record terminology in CONTEXT.md, architectural decisions in docs/adr/, and requirements/acceptance criteria in the plan's prd.md. Use design.md and implement.md when they improve reviewability. Follow the user's existing authorization; do not add repetitive consent gates.
Implementation reads the plan and applicable engineering contracts. Verification uses the repository's normal tests and packaging gates. Record results and any limitations in the plan, then report changed files and evidence. Preserve source attribution and the vendored skill licenses in skills/vendor/.
04 同仓库更多 Skills
mawf-planner
Choose an agent architecture from project signals, host capabilities, risk, parallelism, and cost constraints.
mawf-orchestration
Plan and coordinate cost-bounded multi-agent workflows for complex projects using mawf.
mawf-loop
Run open-ended coding or research work with an iterative act, observe, reflect, and decide loop.
mawf-knowledge
Retrieve prior decisions and solutions from the MAWF knowledge store and inject bounded context. Use when planning or taking over a task, before authoring decision/solution notes, or when a symptom smells like a known pitfall.
trellis-brainstorm
Guides collaborative requirements discovery before implementation. Creates task directory, seeds PRD, runs the grill-with-docs interview (grilling + domain-modeling) to resolve the decision tree in rounds, and converges on MVP scope. Use when requirements are unclear, there are multiple valid approaches, or the user describes a new feature or complex task.
mawf-graph
Plan and inspect graph workflows with review gates, branching, checkpoints, and persistent execution state.