plan-executor
Plan Executor
Role
You are the Tech Lead orchestrator. Your only job is to decompose, dispatch, review, and decide. You NEVER write implementation code or modify source files directly.
Plan File Format
Read $ARGUMENTS and extract tasks. The plan file should contain a task list where
each task has an ID, description, and optional dependencies. Example:
## Tasks
- [ ] T-01: Set up project structure
- [ ] T-02: Implement user model (depends on: T-01)
- [ ] T-03: Add authentication API (depends on: T-01)
- [ ] T-04: Write integration tests (depends on: T-02, T-03)
More from vamdawn/ai-forge
content-summarizer
Fetch, analyze, and summarize web content into structured Obsidian notes. Supports articles, GitHub repositories, and Reddit/HN/Twitter threads. Automatically detects URL type and selects the appropriate fetcher strategy and note template. Triggers include requests like 'summarize this article', 'take notes on this', 'save this repo', 'summarize this thread', or any URL-based request intended to be saved as an Obsidian note.
62git-commit
Create well-formatted atomic git commits with conventional commit messages and emoji. Use when making git commits, splitting large changesets into logical units, or crafting commit messages.
16semver-release
Automated version release workflow. Analyzes git commit history to infer semantic version, auto-detects version files across ecosystems, updates multilingual CHANGELOGs, creates git commit and tag. Use when: (1) user says "release", "publish version", "bump version", (2) user invokes /release command, (3) preparing to release a new version.
16review-doc
Structured document review and quality improvement. Use when the user asks to review, proofread, check, audit, or improve a document (Markdown, text, or any prose file). Triggers include: 'review this doc', 'check this document', 'proofread', 'audit this spec', 'review and fix', or any request to find and fix issues in written documents. Supports reviewing against referenced standards (PRD, design docs, style guides).
15review-context
从 context engineering 角度审查代码、架构文档、prompt 和设计文档。自动识别内容类型,选择 3-5 个最相关维度进行审查,生成含严重等级和改进建议的结构化报告。触发词:review context、CE 审查、上下文工程审查。
9session-summary
分析当前会话内容并按固定格式生成结构化摘要,输出基本信息、会话概要与逐轮明细。触发词:'总结这次会话'、'summarize this session'、'会话总结'、'session summary'、'总结一下'、'生成会话摘要'、'记录本次会话'。
9