planning-with-files 是做什麼的？
使用持久化的 Markdown 檔案進行一般規劃、進度追蹤和知識儲存（Manus 風格工作流程）。適用於多步驟任務、研究專案或一般組織工作，但請勿提及 PRD。若需要 PRD 相關工作，請改用 prd-planner 技能。
使用持久化的 Markdown 檔案進行一般規劃、進度追蹤和知識儲存（Manus 風格工作流程）。適用於多步驟任務、研究專案或一般組織工作，但請勿提及 PRD。若需要 PRD 相關工作，請改用 prd-planner 技能。
這個技能模仿 Manus 工作流程，將規劃、進度追蹤和知識儲存延續到對話之外，透過持久化的 Markdown 檔案來管理。它非常適合處理多步驟任務、研究專案或任何需要結構化組織的工作，但明確避免用於 PRD 相關功能。支援的平台包括 Claude Code、Cursor、Codex 等 AI 代理端。運作方式是透過在專案目錄中建立和維護 Markdown 文件，讓開發者或使用者可以隨時查看或更新計畫、記錄進度、以及儲存關鍵知識，而不會因為 AI 模型的上下文限制而遺失資訊。總之，這是一個輕量級、檔案驅動的專案管理和協作工具。
npx skills add https://github.com/charon-fan/agent-playbook/tree/main/skills/planning-with-filesInstalled? Explore more 研究與資料分析 skills: affaan-m/uspto-database, affaan-m/scholar-evaluation, affaan-m/literature-review · View all 6 →
使用持久化的 Markdown 檔案進行一般規劃、進度追蹤和知識儲存（Manus 風格工作流程）。適用於多步驟任務、研究專案或一般組織工作，但請勿提及 PRD。若需要 PRD 相關工作，請改用 prd-planner 技能。
This repo contains 2 individual skills — each has its own dedicated page.
Security vulnerability expert covering OWASP Top 10 and common security issues. Use when conducting security audits or reviewing code for vulnerabilities.
A universal self-improving agent that learns from ALL skill experiences. Uses multi-memory architecture (semantic + episodic + working) to continuously evolve the codebase. Auto-triggers on skill completion/error with hooks-based self-correction.
USPTO patent and trademark data workflow for official record lookup, PatentSearch queries, TSDR checks, assignment data, and reproducible IP research logs.
Structured scholarly-work evaluation for papers, proposals, literature reviews, methods sections, evidence quality, citation support, and research-writing feedback.
Systematic literature-review workflow for academic, biomedical, technical, and scientific topics, including search planning, source screening, synthesis, citation checks, and evidence logging.
The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.
Agent skill repository discovered by 10x-chat research.
Review backend code for quality, security, maintainability, and best practices based on established checklist rules. Use when the user requests a review, analysis, or improvement of backend files (e.g., `.py`) under the `api/` directory. Do NOT use for frontend files (e.g., `.tsx`, `.ts`, `.js`). Supports pending-change review, code snippets review, and file-focused review.