[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-e600cab3-aac5-4a69-89b4-e76b68cfc49d":3,"$fIZArwfWdflAUASYgZs_SNNiwQ4m_dzobpF-XcAzjxK4":43},{"id":4,"title":5,"description":6,"categoryId":7,"moduleId":8,"tags":9,"prompt":10,"icon":11,"source":12,"sourceUrl":13,"authorId":14,"authorName":15,"isPublic":16,"stars":17,"runs":18,"createdAt":19,"updatedAt":19,"module":20,"category":27,"packages":34},"e600cab3-aac5-4a69-89b4-e76b68cfc49d","build","建立","cat_life_career","mod_other","sickn33,other","---\nname: build\ndescription: build\nrisk: unknown\nsource: community\n---\n\n---\nname: build\ndescription: Feature development pipeline - research, plan, track, and implement major features.\nargument-hint: [subcommand] [name]\nmetadata:\n  author: Shpigford\n  version: \"1.0\"\n---\n\nFeature development pipeline - research, plan, track, and implement major features.\n\n## When to Use\n- You need a structured workflow for building a major feature across research, planning, implementation, and tracking.\n- The task involves moving a feature through named phases such as `research`, `implementation`, `progress`, or `phase`.\n- You want one command to coordinate status, next steps, and phased delivery for a feature effort.\n\n## Instructions\n\nThis command manages a 4-phase feature development workflow for building major features. Parse `$ARGUMENTS` to determine which subcommand to run.\n\n**Arguments provided:** $ARGUMENTS\n\n### Argument Parsing\n\nParse the first word of $ARGUMENTS to determine the subcommand:\n\n- `research [name]` → Run the Research phase\n- `implementation [name]` → Run the Implementation phase\n- `progress [name]` → Run the Progress phase\n- `phase [n] [name]` → Run Phase n of the implementation\n- `status [name]` → Show current status and suggest next step\n- (empty or unrecognized) → Show usage help\n\nIf the feature name is not provided in arguments, you MUST use AskUserQuestion to prompt for it.\n\n---\n\n## Subcommand: Help (empty args)\n\nIf no arguments provided, display this help:\n\n```\n\u002Fbuild - Feature Development Pipeline\n\nSubcommands:\n  \u002Fbuild research [name]        Deep research on a feature idea\n  \u002Fbuild implementation [name]  Create phased implementation plan\n  \u002Fbuild progress [name]        Set up progress tracking\n  \u002Fbuild phase [n] [name]       Execute implementation phase n\n  \u002Fbuild status [name]          Show status and next steps\n\nExample workflow:\n  \u002Fbuild research chat-interface\n  \u002Fbuild implementation chat-interface\n  \u002Fbuild progress chat-interface\n  \u002Fbuild phase 1 chat-interface\n```\n\nThen use AskUserQuestion to ask what they'd like to do:\n\n- question: \"What would you like to do?\"\n- header: \"Action\"\n- multiSelect: false\n- options:\n  - label: \"Start new feature research\"\n    description: \"Begin deep research on a new feature idea\"\n  - label: \"Continue existing feature\"\n    description: \"Work on a feature already in progress\"\n  - label: \"Check status\"\n    description: \"See what step to do next for a feature\"\n\n---\n\n## Subcommand: research\n\n### Step 1: Get Feature Name\n\nIf feature name not in arguments, use AskUserQuestion:\n\n- question: \"What's a short identifier for this feature? (lowercase, hyphens ok - e.g., 'chat-interface', 'user-auth', 'data-export'). Use 'Other' to type it.\"\n- header: \"Feature name\"\n- multiSelect: false\n- options:\n  - label: \"I'll type the name\"\n    description: \"Enter a short, kebab-case identifier for the feature\"\n\n### Step 2: Check for Existing Research\n\nCheck if `docs\u002F{name}\u002FRESEARCH.md` already exists.\n\nIf it exists, use AskUserQuestion:\n\n- question: \"A RESEARCH.md already exists for this feature. What would you like to do?\"\n- header: \"Existing doc\"\n- multiSelect: false\n- options:\n  - label: \"Overwrite\"\n    description: \"Replace existing research with fresh exploration\"\n  - label: \"Append\"\n    description: \"Add new research below existing content\"\n  - label: \"Skip\"\n    description: \"Keep existing research, suggest next step\"\n\nIf \"Skip\" selected, suggest running `\u002Fbuild implementation {name}` and exit.\n\n### Step 3: Gather Feature Context\n\nUse AskUserQuestion to understand the feature:\n\n- question: \"Describe the feature you want to build. What problem does it solve? What should it do? (Use 'Other' to describe)\"\n- header: \"Description\"\n- multiSelect: false\n- options:\n  - label: \"I'll describe it\"\n    description: \"Provide a detailed description of the feature\"\n\n### Step 4: Research Scope\n\nUse AskUserQuestion:\n\n- question: \"What aspects should the research focus on?\"\n- header: \"Focus areas\"\n- multiSelect: true\n- options:\n  - label: \"Technical implementation\"\n    description: \"APIs, libraries, architecture patterns\"\n  - label: \"UI\u002FUX design\"\n    description: \"Interface design, user flows, interactions\"\n  - label: \"Data requirements\"\n    description: \"What data to store, schemas, privacy\"\n  - label: \"Platform capabilities\"\n    description: \"OS APIs, system integrations, permissions\"\n\n### Step 5: Conduct Deep Research\n\nNow conduct DEEP research on the feature:\n\n1. **Codebase exploration**: Understand existing patterns, similar features, relevant code\n2. **Web search**: Research best practices, similar implementations, relevant APIs\n3. **Technical deep-dive**: Explore specific technologies, libraries, frameworks\n4. **Use AskUserQuestion FREQUENTLY**: Validate assumptions, clarify requirements, get input on decisions\n\nResearch should cover:\n- Problem definition and user needs\n- Technical approaches and trade-offs\n- Required data models and storage\n- UI\u002FUX considerations\n- Integration points with existing code\n- Potential challenges and risks\n- Recommended approach with rationale\n\n### Step 6: Write Research Document\n\nCreate the directory if needed: `docs\u002F{name}\u002F`\n\nWrite findings to `docs\u002F{name}\u002FRESEARCH.md` with this structure:\n\n```markdown\n# {Feature Name} Research\n\n## Overview\n[Brief description of the feature and its purpose]\n\n## Problem Statement\n[What problem this solves, why it matters]\n\n## User Stories \u002F Use Cases\n[Concrete examples of how users will use this]\n\n## Technical Research\n\n### Approach Options\n[Different ways to implement this, with pros\u002Fcons]\n\n### Recommended Approach\n[The approach you recommend and why]\n\n### Required Technologies\n[APIs, libraries, frameworks needed]\n\n### Data Requirements\n[What data needs to be stored\u002Ftracked]\n\n## UI\u002FUX Considerations\n[Interface design thoughts, user flows]\n\n## Integration Points\n[How this connects to existing code\u002Ffeatures]\n\n## Risks and Challenges\n[Potential issues and mitigation strategies]\n\n## Open Questions\n[Things that still need to be decided]\n\n## References\n[Links to relevant documentation, examples, articles]\n```\n\n### Step 7: Next Step\n\nAfter writing the research doc, inform the user:\n\n\"Research complete! Document saved to `docs\u002F{name}\u002FRESEARCH.md`\n\n**Next step:** Run `\u002Fbuild implementation {name}` to create a phased implementation plan.\"\n\n---\n\n## Subcommand: implementation\n\n### Step 1: Get Feature Name\n\nIf feature name not in arguments, use AskUserQuestion to prompt for it (same as research phase).\n\n### Step 2: Verify Research Exists\n\nCheck if `docs\u002F{name}\u002FRESEARCH.md` exists.\n\nIf it does NOT exist:\n- Inform user: \"No research document found at `docs\u002F{name}\u002FRESEARCH.md`\"\n- Suggest: \"Run `\u002Fbuild research {name}` first to create the research document.\"\n- Exit\n\n### Step 3: Check for Existing Implementation Doc\n\nCheck if `docs\u002F{name}\u002FIMPLEMENTATION.md` already exists.\n\nIf it exists, use AskUserQuestion:\n\n- question: \"An IMPLEMENTATION.md already exists. What would you like to do?\"\n- header: \"Existing doc\"\n- multiSelect: false\n- options:\n  - label: \"Overwrite\"\n    description: \"Create a fresh implementation plan\"\n  - label: \"Append\"\n    description: \"Add new phases below existing content\"\n  - label: \"Skip\"\n    description: \"Keep existing plan, suggest next step\"\n\nIf \"Skip\" selected, suggest running `\u002Fbuild progress {name}` and exit.\n\n### Step 4: Read Research Document\n\nRead `docs\u002F{name}\u002FRESEARCH.md` to understand:\n- The recommended approach\n- Technical requirements\n- Data models needed\n- UI\u002FUX design\n- Integration points\n\n### Step 5: Design Implementation Phases\n\nBreak the research into practical implementation phases. Each phase should:\n- Be independently valuable (deliver something usable)\n- Be small enough to complete in a focused session\n- Build on previous phases\n- Have clear success criteria\n\nUse AskUserQuestion to validate phase breakdown:\n\n- question: \"How granular should the implementation phases be?\"\n- header: \"Phase size\"\n- multiSelect: false\n- options:\n  - label: \"Small phases (1-2 hours)\"\n    description: \"Many focused phases, easier to track progress\"\n  - label: \"Medium phases (half day)\"\n    description: \"Balanced approach, moderate number of phases\"\n  - label: \"Large phases (full day)\"\n    description: \"Fewer phases, each delivering significant functionality\"\n\n### Step 6: Conduct Phase Research\n\nFor each phase you're planning, do targeted research:\n- Web search for implementation specifics\n- Review relevant code in the codebase\n- Identify dependencies between phases\n\nUse AskUserQuestion for any uncertainties about phase ordering or scope.\n\n### Step 7: Write Implementation Document\n\nWrite to `docs\u002F{name}\u002FIMPLEMENTATION.md` with this structure:\n\n```markdown\n# {Feature Name} Implementation Plan\n\n## Overview\n[Brief recap of what we're building and the approach from research]\n\n## Prerequisites\n[What needs to be in place before starting]\n\n## Phase Summary\n[Quick overview of all phases]\n\n---\n\n## Phase 1: [Phase Title]\n\n### Objective\n[What this phase accomplishes]\n\n### Rationale\n[Why this phase comes first, what it enables]\n\n### Tasks\n- [ ] Task 1\n- [ ] Task 2\n- [ ] Task 3\n\n### Success Criteria\n[How to verify this phase is complete]\n\n### Files Likely Affected\n[List of files that will probably need changes]\n\n---\n\n## Phase 2: [Phase Title]\n\n[Same structure as Phase 1]\n\n---\n\n[Continue for all phases]\n\n---\n\n## Post-Implementation\n- [ ] Documentation updates\n- [ ] Testing strategy\n- [ ] Performance validation\n\n## Notes\n[Any additional context or decisions made during planning]\n```\n\n### Step 8: Next Step\n\nAfter writing the implementation doc, inform the user:\n\n\"Implementation plan complete! Document saved to `docs\u002F{name}\u002FIMPLEMENTATION.md`\n\n**Next step:** Run `\u002Fbuild progress {name}` to set up progress tracking.\"\n\n---\n\n## Subcommand: progress\n\n### Step 1: Get Feature Name\n\nIf feature name not in arguments, use AskUserQuestion to prompt for it.\n\n### Step 2: Verify Implementation Doc Exists\n\nCheck if `docs\u002F{name}\u002FIMPLEMENTATION.md` exists.\n\nIf it does NOT exist:\n- Inform user: \"No implementation document found at `docs\u002F{name}\u002FIMPLEMENTATION.md`\"\n- Suggest: \"Run `\u002Fbuild implementation {name}` first.\"\n- Exit\n\n### Step 3: Check for Existing Progress Doc\n\nCheck if `docs\u002F{name}\u002FPROGRESS.md` already exists.\n\nIf it exists, use AskUserQuestion:\n\n- question: \"A PROGRESS.md already exists. What would you like to do?\"\n- header: \"Existing doc\"\n- multiSelect: false\n- options:\n  - label: \"Overwrite\"\n    description: \"Start fresh progress tracking\"\n  - label: \"Keep existing\"\n    description: \"Keep current progress, suggest next step\"\n\nIf \"Keep existing\" selected, read the progress doc and suggest the next incomplete phase.\n\n### Step 4: Read Implementation Document\n\nRead `docs\u002F{name}\u002FIMPLEMENTATION.md` to extract:\n- All phase titles\n- Tasks within each phase\n- Success criteria\n\n### Step 5: Create Progress Document\n\nWrite to `docs\u002F{name}\u002FPROGRESS.md` with this structure:\n\n```markdown\n# {Feature Name} Progress\n\n## Status: Phase 1 - Not Started\n\n## Quick Reference\n- Research: `docs\u002F{name}\u002FRESEARCH.md`\n- Implementation: `docs\u002F{name}\u002FIMPLEMENTATION.md`\n\n---\n\n## Phase Progress\n\n### Phase 1: [Title from Implementation]\n**Status:** Not Started\n\n#### Tasks Completed\n- (none yet)\n\n#### Decisions Made\n- (none yet)\n\n#### Blockers\n- (none)\n\n---\n\n### Phase 2: [Title]\n**Status:** Not Started\n\n[Same structure]\n\n---\n\n[Continue for all phases]\n\n---\n\n## Session Log\n\n### [Date will be added as work happens]\n- Work completed\n- Decisions made\n- Notes for next session\n\n---\n\n## Files Changed\n(Will be updated as implementation progresses)\n\n## Architectural Decisions\n(Major technical decisions and rationale)\n\n## Lessons Learned\n(What worked, what didn't, what to do differently)\n```\n\n### Step 6: Next Step\n\nAfter creating progress doc:\n\n\"Progress tracking set up! Document saved to `docs\u002F{name}\u002FPROGRESS.md`\n\n**Next step:** Run `\u002Fbuild phase 1 {name}` to begin implementation.\"\n\n---\n\n## Subcommand: phase\n\n### Step 1: Parse Arguments\n\nParse arguments to extract:\n- Phase number (if provided)\n- Feature name (if provided)\n\nIf neither provided, prompt for both using AskUserQuestion.\n\n### Step 2: Get Feature Name\n\nIf feature name not determined, use AskUserQuestion to prompt for it.\n\n### Step 3: Verify All Docs Exist\n\nCheck that all three docs exist:\n- `docs\u002F{name}\u002FRESEARCH.md`\n- `docs\u002F{name}\u002FIMPLEMENTATION.md`\n- `docs\u002F{name}\u002FPROGRESS.md`\n\nIf any missing, inform user which doc is missing and suggest the appropriate `\u002Fbuild` command to create it.\n\n### Step 4: Get Phase Number\n\nIf phase number not in arguments:\n\nRead `docs\u002F{name}\u002FIMPLEMENTATION.md` to extract available phases.\n\nUse AskUserQuestion to let user select:\n\n- question: \"Which phase would you like to work on?\"\n- header: \"Phase\"\n- multiSelect: false\n- options: [dynamically generated from phases found in IMPLEMENTATION.md, marking completed ones]\n\n### Step 5: Read All Context\n\nRead all three documents to fully understand:\n- The research and rationale (RESEARCH.md)\n- The specific phase tasks and success criteria (IMPLEMENTATION.md)\n- Current progress and decisions made (PROGRESS.md)\n\n### Step 6: Deep Research on Phase\n\nBefore starting implementation:\n\n1. **Web search** for specific implementation details relevant to this phase\n2. **Codebase exploration** for relevant existing code\n3. **Use AskUserQuestion** to clarify any ambiguities about the phase requirements\n\n### Step 7: Execute Phase Work\n\nBegin implementing the phase:\n\n1. Work through each task in the phase\n2. Use AskUserQuestion frequently for implementation decisions\n3. Follow the \"Always Works\" philosophy - test as you go\n4. Document decisions in PROGRESS.md as you make them\n\n### Step 8: Update Progress Document\n\nAs you work, update `docs\u002F{name}\u002FPROGRESS.md`:\n\n- Mark tasks as completed\n- Record decisions made and why\n- Note any blockers encountered\n- List files changed\n- Add architectural decisions\n- Update the session log with today's work\n\nUpdate the phase status:\n- \"In Progress\" when starting\n- \"Completed\" when all tasks done and success criteria met\n\n### Step 9: Next Step\n\nAfter completing the phase:\n\n1. Read PROGRESS.md to determine next incomplete phase\n2. Inform user of completion and suggest next action:\n\n\"Phase {n} complete! Progress updated in `docs\u002F{name}\u002FPROGRESS.md`\n\n**Next step:** Run `\u002Fbuild phase {n+1} {name}` to continue with [next phase title].\"\n\nOr if all phases complete:\n\n\"All phases complete! The {feature name} feature implementation is done.\n\nConsider:\n- Running tests to verify everything works\n- Updating documentation\n- Creating a PR for review\"\n\n---\n\n## Subcommand: status\n\n### Step 1: Get Feature Name\n\nIf feature name not in arguments, use AskUserQuestion to prompt for it.\n\n### Step 2: Check Which Docs Exist\n\nCheck for existence of:\n- `docs\u002F{name}\u002FRESEARCH.md`\n- `docs\u002F{name}\u002FIMPLEMENTATION.md`\n- `docs\u002F{name}\u002FPROGRESS.md`\n\n### Step 3: Determine Status and Next Step\n\nBased on which docs exist:\n\n**No docs exist:**\n\"No documents found for feature '{name}'.\n**Next step:** Run `\u002Fbuild research {name}` to start.\"\n\n**Only RESEARCH.md exists:**\n\"Research complete for '{name}'.\n**Next step:** Run `\u002Fbuild implementation {name}` to create implementation plan.\"\n\n**RESEARCH.md and IMPLEMENTATION.md exist:**\n\"Research and implementation plan complete for '{name}'.\n**Next step:** Run `\u002Fbuild progress {name}` to set up progress tracking.\"\n\n**All three exist:**\nRead PROGRESS.md to find current phase status.\n\"Feature '{name}' is in progress.\n**Current status:** [Phase X - status]\n**Next step:** Run `\u002Fbuild phase {next incomplete phase} {name}` to continue.\"\n\nIf all phases complete:\n\"Feature '{name}' implementation is complete!\"\n\n---\n\n## Important Guidelines\n\n### Use AskUserQuestion Liberally\n\nThroughout all phases, use AskUserQuestion whenever:\n- There's ambiguity in requirements\n- Multiple approaches are possible\n- You need to validate an assumption\n- A decision will significantly impact the implementation\n- You're unsure about scope or priority\n\n### Deep Research Expectations\n\n\"Deep research\" means:\n- Multiple web searches on different aspects\n- Thorough codebase exploration\n- Reading relevant documentation\n- Considering multiple approaches\n- Understanding trade-offs\n\nDon't rush through research - it's the foundation for good implementation.\n\n### Progress Tracking\n\nKeep PROGRESS.md updated in real-time during phase work:\n- Don't wait until the end to update\n- Record decisions as they're made\n- Note blockers immediately\n- This creates valuable context for future sessions\n\n### Scope Management\n\nA key purpose of this workflow is preventing scope creep:\n- Each phase should have clear boundaries\n- If new requirements emerge, note them for future phases\n- Don't expand the current phase's scope mid-implementation\n- Use AskUserQuestion to validate if something is in\u002Fout of scope\n\n### Always Works Philosophy\n\nWhen implementing phases:\n- Test changes as you make them\n- Don't assume code works - verify it\n- If something doesn't work, fix it before moving on\n- The goal is working software, not just written code\n\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n","","imported","https:\u002F\u002Fgithub.com\u002Fsickn33\u002Fantigravity-awesome-skills","user_system_seed","SkillOPIC",true,176,477,"2026-05-16 13:09:28",{"id":8,"name":21,"slug":22,"icon":23,"description":24,"sort":25,"createdAt":26},"其他","other","mdi-page-next-outline","其他类型Skill",5,"2026-05-16 12:53:40",{"id":7,"name":28,"slug":29,"icon":30,"description":31,"moduleId":8,"sort":32,"skillCount":33,"createdAt":26},"职场发展","career","mdi-briefcase-outline","面试准备、简历优化、职业规划",4,575,[35],{"id":36,"skillId":4,"version":37,"fileName":38,"fileSize":39,"filePath":40,"fileHash":41,"manifest":42,"createdAt":19},"34946b13-8d66-4270-8df3-6eb85c95d52d","1.0.0","build.zip",5568,"uploads\u002Fskills\u002Fe600cab3-aac5-4a69-89b4-e76b68cfc49d\u002Fbuild.zip","f630df67555683130f4908059907efde5a3af91e4ff45f52b165b30a2320e68a","[{\"path\":\"SKILL.md\",\"isDirectory\":false,\"size\":17400}]",{"code":44,"message":45,"data":46},200,"success",{"items":47,"stats":48,"page":51},[],{"averageRating":49,"totalRatings":49,"ratingCounts":50},0,[49,49,49,49,49],{"limit":52,"offset":49,"hasMore":53,"nextOffset":52,"ratedOnly":16},15,false]