[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79YMAX7NFYDFXFZH2TJS7SS":3,"skill-same:01M79YMAX7NFYDFXFZH2TJS7SS":53},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":13,"repositoryHtmlUrl":26,"repositoryHomepageUrl":6,"ownerHtmlUrl":27,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":28,"install":29,"resources":42},"01M79YMAX7NFYDFXFZH2TJS7SS","planning-with-files",null,"Transforms workflow to use Manus-style persistent markdown files for planning, progress tracking, and knowledge storage. Use when starting complex tasks, multi-step projects, research tasks, or when the user mentions planning, organizing work, tracking progress, or wants structured output.","KrismithReddy12\u002Fclaude-code-templates","KrismithReddy12","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F182916557?v=4","01M79T8DNGJRHG48G3H3Q02MK8","01M79TA8ZWV2PP7R4ARWVYWZFE",0,"MIT","https:\u002F\u002Fgithub.com\u002FKrismithReddy12\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fplanning-with-files\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: planning-with-files\ndescription: Transforms workflow to use Manus-style persistent markdown files for planning, progress tracking, and knowledge storage. Use when starting complex tasks, multi-step projects, research tasks, or when the user mentions planning, organizing work, tracking progress, or wants structured output.\n---\n\n# Planning with Files\n\nWork like Manus: Use persistent markdown files as your \"working memory on disk.\"\n\n## Quick Start\n\nBefore ANY complex task:\n\n1. **Create `task_plan.md`** in the working directory\n2. **Define phases** with checkboxes\n3. **Update after each phase** - mark [x] and change status\n4. **Read before deciding** - refresh goals in attention window\n\n## The 3-File Pattern\n\nFor every non-trivial task, create THREE files:\n\n| File | Purpose | When to Update |\n|------|---------|----------------|\n| `task_plan.md` | Track phases and progress | After each phase |\n| `notes.md` | Store findings and research | During research |\n| `[deliverable].md` | Final output | At completion |\n\n## Core Workflow\n\n```\nLoop 1: Create task_plan.md with goal and phases\nLoop 2: Research → save to notes.md → update task_plan.md\nLoop 3: Read notes.md → create deliverable → update task_plan.md\nLoop 4: Deliver final output\n```\n\n### The Loop in Detail\n\n**Before each major action:**\n```bash\nRead task_plan.md  # Refresh goals in attention window\n```\n\n**After each phase:**\n```bash\nEdit task_plan.md  # Mark [x], update status\n```\n\n**When storing information:**\n```bash\nWrite notes.md     # Don't stuff context, store in file\n```\n\n## task_plan.md Template\n\nCreate this file FIRST for any complex task:\n\n```markdown\n# Task Plan: [Brief Description]\n\n## Goal\n[One sentence describing the end state]\n\n## Phases\n- [ ] Phase 1: Plan and setup\n- [ ] Phase 2: Research\u002Fgather information\n- [ ] Phase 3: Execute\u002Fbuild\n- [ ] Phase 4: Review and deliver\n\n## Key Questions\n1. [Question to answer]\n2. [Question to answer]\n\n## Decisions Made\n- [Decision]: [Rationale]\n\n## Errors Encountered\n- [Error]: [Resolution]\n\n## Status\n**Currently in Phase X** - [What I'm doing now]\n```\n\n## notes.md Template\n\nFor research and findings:\n\n```markdown\n# Notes: [Topic]\n\n## Sources\n\n### Source 1: [Name]\n- URL: [link]\n- Key points:\n  - [Finding]\n  - [Finding]\n\n## Synthesized Findings\n\n### [Category]\n- [Finding]\n- [Finding]\n```\n\n## Critical Rules\n\n### 1. ALWAYS Create Plan First\nNever start a complex task without `task_plan.md`. This is non-negotiable.\n\n### 2. Read Before Decide\nBefore any major decision, read the plan file. This keeps goals in your attention window.\n\n### 3. Update After Act\nAfter completing any phase, immediately update the plan file:\n- Mark completed phases with [x]\n- Update the Status section\n- Log any errors encountered\n\n### 4. Store, Don't Stuff\nLarge outputs go to files, not context. Keep only paths in working memory.\n\n### 5. Log All Errors\nEvery error goes in the \"Errors Encountered\" section. This builds knowledge for future tasks.\n\n## When to Use This Pattern\n\n**Use 3-file pattern for:**\n- Multi-step tasks (3+ steps)\n- Research tasks\n- Building\u002Fcreating something\n- Tasks spanning multiple tool calls\n- Anything requiring organization\n\n**Skip for:**\n- Simple questions\n- Single-file edits\n- Quick lookups\n\n## Anti-Patterns to Avoid\n\n| Don't | Do Instead |\n|-------|------------|\n| Use TodoWrite for persistence | Create `task_plan.md` file |\n| State goals once and forget | Re-read plan before each decision |\n| Hide errors and retry | Log errors to plan file |\n| Stuff everything in context | Store large content in files |\n| Start executing immediately | Create plan file FIRST |\n\n## Advanced Patterns\n\nSee [reference.md](reference.md) for:\n- Attention manipulation techniques\n- Error recovery patterns\n- Context optimization from Manus\n\nSee [examples.md](examples.md) for:\n- Real task examples\n- Complex workflow patterns\n","# Planning with Files\n\nWork like Manus: Use persistent markdown files as your \"working memory on disk.\"\n\n## Quick Start\n\nBefore ANY complex task:\n\n1. **Create `task_plan.md`** in the working directory\n2. **Define phases** with checkboxes\n3. **Update after each phase** - mark [x] and change status\n4. **Read before deciding** - refresh goals in attention window\n\n## The 3-File Pattern\n\nFor every non-trivial task, create THREE files:\n\n| File | Purpose | When to Update |\n|------|---------|----------------|\n| `task_plan.md` | Track phases and progress | After each phase |\n| `notes.md` | Store findings and research | During research |\n| `[deliverable].md` | Final output | At completion |\n\n## Core Workflow\n\n```\nLoop 1: Create task_plan.md with goal and phases\nLoop 2: Research → save to notes.md → update task_plan.md\nLoop 3: Read notes.md → create deliverable → update task_plan.md\nLoop 4: Deliver final output\n```\n\n### The Loop in Detail\n\n**Before each major action:**\n```bash\nRead task_plan.md  # Refresh goals in attention window\n```\n\n**After each phase:**\n```bash\nEdit task_plan.md  # Mark [x], update status\n```\n\n**When storing information:**\n```bash\nWrite notes.md     # Don't stuff context, store in file\n```\n\n## task_plan.md Template\n\nCreate this file FIRST for any complex task:\n\n```markdown\n# Task Plan: [Brief Description]\n\n## Goal\n[One sentence describing the end state]\n\n## Phases\n- [ ] Phase 1: Plan and setup\n- [ ] Phase 2: Research\u002Fgather information\n- [ ] Phase 3: Execute\u002Fbuild\n- [ ] Phase 4: Review and deliver\n\n## Key Questions\n1. [Question to answer]\n2. [Question to answer]\n\n## Decisions Made\n- [Decision]: [Rationale]\n\n## Errors Encountered\n- [Error]: [Resolution]\n\n## Status\n**Currently in Phase X** - [What I'm doing now]\n```\n\n## notes.md Template\n\nFor research and findings:\n\n```markdown\n# Notes: [Topic]\n\n## Sources\n\n### Source 1: [Name]\n- URL: [link]\n- Key points:\n  - [Finding]\n  - [Finding]\n\n## Synthesized Findings\n\n### [Category]\n- [Finding]\n- [Finding]\n```\n\n## Critical Rules\n\n### 1. ALWAYS Create Plan First\nNever start a complex task without `task_plan.md`. This is non-negotiable.\n\n### 2. Read Before Decide\nBefore any major decision, read the plan file. This keeps goals in your attention window.\n\n### 3. Update After Act\nAfter completing any phase, immediately update the plan file:\n- Mark completed phases with [x]\n- Update the Status section\n- Log any errors encountered\n\n### 4. Store, Don't Stuff\nLarge outputs go to files, not context. Keep only paths in working memory.\n\n### 5. Log All Errors\nEvery error goes in the \"Errors Encountered\" section. This builds knowledge for future tasks.\n\n## When to Use This Pattern\n\n**Use 3-file pattern for:**\n- Multi-step tasks (3+ steps)\n- Research tasks\n- Building\u002Fcreating something\n- Tasks spanning multiple tool calls\n- Anything requiring organization\n\n**Skip for:**\n- Simple questions\n- Single-file edits\n- Quick lookups\n\n## Anti-Patterns to Avoid\n\n| Don't | Do Instead |\n|-------|------------|\n| Use TodoWrite for persistence | Create `task_plan.md` file |\n| State goals once and forget | Re-read plan before each decision |\n| Hide errors and retry | Log errors to plan file |\n| Stuff everything in context | Store large content in files |\n| Start executing immediately | Create plan file FIRST |\n\n## Advanced Patterns\n\nSee [reference.md](reference.md) for:\n- Attention manipulation techniques\n- Error recovery patterns\n- Context optimization from Manus\n\nSee [examples.md](examples.md) for:\n- Real task examples\n- Complex workflow patterns\n",{"name":5,"description":7},"main","e3744adb7654df443f12927f3e001252b3a26b6d","cli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fplanning-with-files","https:\u002F\u002Fgithub.com\u002FKrismithReddy12\u002Fclaude-code-templates","https:\u002F\u002Fgithub.com\u002FKrismithReddy12","2026-07-29 08:15:10",{"source":8,"skillName":5,"commands":30,"prompt":40,"zipAvailable":41},[31,34,37],{"tool":32,"command":33},"npx","npx skills add KrismithReddy12\u002Fclaude-code-templates --skill planning-with-files",{"tool":35,"command":36},"bunx","bunx skills add KrismithReddy12\u002Fclaude-code-templates --skill planning-with-files",{"tool":38,"command":39},"pnpm","pnpm dlx skills add KrismithReddy12\u002Fclaude-code-templates --skill planning-with-files","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FKrismithReddy12\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fplanning-with-files\u002FSKILL.md",true,[43,49],{"path":44,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":47,"sourceHtmlUrl":48},"examples.md","REFERENCE","参考文档",4426,"https:\u002F\u002Fgithub.com\u002FKrismithReddy12\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fplanning-with-files\u002Fexamples.md",{"path":50,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":51,"sourceHtmlUrl":52},"reference.md",3478,"https:\u002F\u002Fgithub.com\u002FKrismithReddy12\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fplanning-with-files\u002Freference.md",[54,61,70,77,84,91],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":18},"01M79YMXJ07S2BQVB7JAM3657Q","zapier-make-patterns","No-code automation democratizes workflow building. Zapier and Make (formerly Integromat) let non-developers automate business processes without writing code. But no-code doesn't mean no-complexity - these platforms have their own patterns, pitfalls, and breaking points.  This skill covers when to use which platform, how to build reliable automations, and when to graduate to code-based solutions. Key insight: Zapier optimizes for simplicity and integrations (7000+ apps), Make optimizes for power","https:\u002F\u002Fgithub.com\u002FKrismithReddy12\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fzapier-make-patterns\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":65,"licenseFileUrl":66,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":18},"01M79YMVPMK3Y4JDP2KDJKQ2ZD","yeet","Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).","Apache-2.0","https:\u002F\u002Fgithub.com\u002FKrismithReddy12\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FKrismithReddy12\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":18},"01M79YMMQ4XXMPJHDQHY8FR7ME","workflow-automation","Workflow automation is the infrastructure that makes AI agents reliable. Without durable execution, a network hiccup during a 10-step payment flow means lost money and angry customers. With it, workflows resume exactly where they left off.  This skill covers the platforms (n8n, Temporal, Inngest) and patterns (sequential, parallel, orchestrator-worker) that turn brittle scripts into production-grade automation.  Key insight: The platforms make different tradeoffs. n8n optimizes for accessibility","https:\u002F\u002Fgithub.com\u002FKrismithReddy12\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fworkflow-automation\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":18},"01M79YMHQY3CP1XXMQ00TGQFAW","trigger-dev","Trigger.dev expert for background jobs, AI workflows, and reliable async execution with excellent developer experience and TypeScript-first design. Use when: trigger.dev, trigger dev, background task, ai background job, long running task.","https:\u002F\u002Fgithub.com\u002FKrismithReddy12\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Ftrigger-dev\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":18},"01M79YME4Z3DRW0MT6BNYW1D7P","slack-automation","Automate Slack workspace operations including messaging, search, channel management, and reaction workflows through Composio's Slack toolkit.","https:\u002F\u002Fgithub.com\u002FKrismithReddy12\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fslack-automation\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":18},"01M79YM6F8897378TGY85HNFNA","n8n-workflow-patterns","Proven workflow architectural patterns from real n8n workflows. Use when building new workflows, designing workflow structure, choosing workflow patterns, planning workflow architecture, or asking about webhook processing, HTTP API integration, database operations, AI agent workflows, or scheduled tasks.","https:\u002F\u002Fgithub.com\u002FKrismithReddy12\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fn8n\u002Fn8n-workflow-patterns\u002FSKILL.md",[],[]]