[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7A3JBAZS4PJAVCSRW5GY440":3,"skill-same:01M7A3JBAZS4PJAVCSRW5GY440":46},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":14,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M7A3JBAZS4PJAVCSRW5GY440","feature-development-planner",null,"Research repository structure and requirements, then create a complete feature development plan in docs\u002Fplans. If invoked without arguments, automatically researches the repo and proposes new features for the user to choose from. Supports explicit feature requests and exploratory research.","eovipmak\u002Fcrowdsec-ui","eovipmak","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F62509465?v=4","01M7A3HPVDTMMHRZZ85QBQ4KDD","Tran Nguyen Tin","01M7A3HPW3309JAMP1HRW73J1C",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Feovipmak\u002Fcrowdsec-ui\u002Fblob\u002Fmain\u002F.commandcode\u002Fskills\u002Ffeature-development-planner\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: feature-development-planner\ndescription: Research repository structure and requirements, then create a complete feature development plan in docs\u002Fplans. If invoked without arguments, automatically researches the repo and proposes new features for the user to choose from. Supports explicit feature requests and exploratory research.\nargument-hint: \"[feature or requirement — leave empty to auto-research and propose new features]\"\n---\n\n# Feature Development Planner\n\nCreate an implementation-ready plan without changing source code. Supports two modes: (a) planned feature with explicit requirements, (b) exploratory research to propose new features. **Default invocation (no arguments) automatically enters exploratory research.**\n\n## Workflow\n\n1. Read `AGENTS.md`, the relevant `README`, package\u002Fmodule manifests, existing plans, and repository structure.\n2. Determine mode — **if no argument is given, default to exploratory research automatically (do not ask for clarification, do not wait for extra input):**\n   - **Default \u002F Exploratory (no args, empty prompt, or phrases like `research new features`):** Analyze repository structure, existing features, user flows, TODOs\u002Fopen issues, domain gaps, and competitor\u002Fcommon patterns for this project type. Enumerate 3-5 candidate features ranked by user value and implementation cost, then select the top proposal with clear rationale. Document rejected candidates briefly.\n   - **Explicit feature:** Search for related features, interfaces, conventions, deployment files, and documentation before proposing files or APIs.\n3. Extract requirements from the prompt and repository evidence. For default\u002Fexploratory mode, derive requirements from the ranked candidates and repo evidence. Record explicit assumptions for details that are not specified.\n4. Choose the smallest architecture that fits existing patterns. Preserve project constraints such as native deployment, single-admin security, or no database when they apply.\n5. Write an English Markdown plan under `docs\u002Fplans\u002F` using a descriptive lowercase-hyphenated filename. Include the current date when the repository convention uses dates. For default invocation, include the ranked candidates and a recommendation in one plan; ask for a choice only when interactive selection is explicitly requested.\n\n## Required plan content\n\n- Goal and non-goals.\n- Current-state findings and relevant files. For default\u002Fexploratory mode, also include research summary: existing feature inventory, candidate features considered (ranked 3-5), selection rationale, and rejected candidates.\n- Proposed architecture and data\u002Fcontrol flow.\n- Exact files or directories to create and modify.\n- Interfaces, schemas, routes, commands, and configuration contracts.\n- Ordered implementation tasks with dependencies and parallelization notes.\n- Acceptance criteria and verification commands\u002Fchecks.\n- Security, compatibility, migration, and operational considerations.\n- Risks, unresolved assumptions, and reviewer ownership.\n\n## Rules\n\n- Do not implement code, modify existing source, or create kanban tasks while creating the plan.\n- Do not invent APIs, commands, dependencies, or test commands without labeling them as decisions to validate.\n- Prefer existing project patterns over new abstractions.\n- Keep scope lean and explicitly exclude unrelated infrastructure.\n- Explicitly exclude CI\u002FCD, unit tests, testing infrastructure, and monitoring\u002Fobservability (Grafana\u002FPrometheus\u002Flogging platforms, alerting) unless the user explicitly requests them. Do not add pipeline files, test scaffolding, or dashboards to the plan.\n- Do not plan feature development for the following crowdsec (cscli) commands: appsec-rules, appsec-configs, config, setup, support, hubtest, completion, simulation, versions, explain.\n- **Default behavior:** When invoked without arguments, immediately research the repository and write the ranked proposal; do not pause for clarification or selection unless explicitly requested.\n- If requirements are materially ambiguous in explicit mode, ask focused questions; otherwise proceed with documented assumptions.\n- After writing, reread the plan and check that every requirement maps to a task and acceptance criterion.\n\n## Completion report\n\nState the plan path, key decisions, assumptions, dependencies, and any questions that must be answered before implementation. For default invocation, also list the candidate features proposed and how the user can select one to proceed.\n","# Feature Development Planner\n\nCreate an implementation-ready plan without changing source code. Supports two modes: (a) planned feature with explicit requirements, (b) exploratory research to propose new features. **Default invocation (no arguments) automatically enters exploratory research.**\n\n## Workflow\n\n1. Read `AGENTS.md`, the relevant `README`, package\u002Fmodule manifests, existing plans, and repository structure.\n2. Determine mode — **if no argument is given, default to exploratory research automatically (do not ask for clarification, do not wait for extra input):**\n   - **Default \u002F Exploratory (no args, empty prompt, or phrases like `research new features`):** Analyze repository structure, existing features, user flows, TODOs\u002Fopen issues, domain gaps, and competitor\u002Fcommon patterns for this project type. Enumerate 3-5 candidate features ranked by user value and implementation cost, then select the top proposal with clear rationale. Document rejected candidates briefly.\n   - **Explicit feature:** Search for related features, interfaces, conventions, deployment files, and documentation before proposing files or APIs.\n3. Extract requirements from the prompt and repository evidence. For default\u002Fexploratory mode, derive requirements from the ranked candidates and repo evidence. Record explicit assumptions for details that are not specified.\n4. Choose the smallest architecture that fits existing patterns. Preserve project constraints such as native deployment, single-admin security, or no database when they apply.\n5. Write an English Markdown plan under `docs\u002Fplans\u002F` using a descriptive lowercase-hyphenated filename. Include the current date when the repository convention uses dates. For default invocation, include the ranked candidates and a recommendation in one plan; ask for a choice only when interactive selection is explicitly requested.\n\n## Required plan content\n\n- Goal and non-goals.\n- Current-state findings and relevant files. For default\u002Fexploratory mode, also include research summary: existing feature inventory, candidate features considered (ranked 3-5), selection rationale, and rejected candidates.\n- Proposed architecture and data\u002Fcontrol flow.\n- Exact files or directories to create and modify.\n- Interfaces, schemas, routes, commands, and configuration contracts.\n- Ordered implementation tasks with dependencies and parallelization notes.\n- Acceptance criteria and verification commands\u002Fchecks.\n- Security, compatibility, migration, and operational considerations.\n- Risks, unresolved assumptions, and reviewer ownership.\n\n## Rules\n\n- Do not implement code, modify existing source, or create kanban tasks while creating the plan.\n- Do not invent APIs, commands, dependencies, or test commands without labeling them as decisions to validate.\n- Prefer existing project patterns over new abstractions.\n- Keep scope lean and explicitly exclude unrelated infrastructure.\n- Explicitly exclude CI\u002FCD, unit tests, testing infrastructure, and monitoring\u002Fobservability (Grafana\u002FPrometheus\u002Flogging platforms, alerting) unless the user explicitly requests them. Do not add pipeline files, test scaffolding, or dashboards to the plan.\n- Do not plan feature development for the following crowdsec (cscli) commands: appsec-rules, appsec-configs, config, setup, support, hubtest, completion, simulation, versions, explain.\n- **Default behavior:** When invoked without arguments, immediately research the repository and write the ranked proposal; do not pause for clarification or selection unless explicitly requested.\n- If requirements are materially ambiguous in explicit mode, ask focused questions; otherwise proceed with documented assumptions.\n- After writing, reread the plan and check that every requirement maps to a task and acceptance criterion.\n\n## Completion report\n\nState the plan path, key decisions, assumptions, dependencies, and any questions that must be answered before implementation. For default invocation, also list the candidate features proposed and how the user can select one to proceed.\n",{"name":5,"description":7,"argument-hint":24},"[feature or requirement — leave empty to auto-research and propose new features]","main","6de4714436264d026cecebf59af8e2a8ae8f1450",".commandcode\u002Fskills\u002Ffeature-development-planner","https:\u002F\u002Fgithub.com\u002Feovipmak\u002Fcrowdsec-ui","https:\u002F\u002Fgithub.com\u002Feovipmak","tntin.id.vn","2026-08-21 14:35:58",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add eovipmak\u002Fcrowdsec-ui --skill feature-development-planner",{"tool":38,"command":39},"bunx","bunx skills add eovipmak\u002Fcrowdsec-ui --skill feature-development-planner",{"tool":41,"command":42},"pnpm","pnpm dlx skills add eovipmak\u002Fcrowdsec-ui --skill feature-development-planner","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Feovipmak\u002Fcrowdsec-ui\u002Fblob\u002Fmain\u002F.commandcode\u002Fskills\u002Ffeature-development-planner\u002FSKILL.md",true,[],[47,54,61,66,73,80],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M7A3M56ND4QK41F336TRD72T","plan-task-breakdown","Convert a development plan in docs\u002Fplans into self-contained, dependency-aware Markdown tasks for agents under docs\u002Fkanban\u002F\u003Cdate>_\u003Cplan-name>. Use when asked to break down, decompose, or prepare a plan for parallel agent execution.","https:\u002F\u002Fgithub.com\u002Feovipmak\u002Fcrowdsec-ui\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fplan-task-breakdown\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7A3M1QVMVCKY014J5Z7G76B","kanban-task-coordinator","Coordinate agents to execute a dependency-aware task set from a docs\u002Fkanban directory, including reviewing tasks, assigning work, collecting changes, verifying results, and handling blockers. Use when asked to execute or coordinate a kanban plan such as docs\u002Fkanban\u002F2026-08-04_deep-research-report.","https:\u002F\u002Fgithub.com\u002Feovipmak\u002Fcrowdsec-ui\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fkanban-task-coordinator\u002FSKILL.md",[],[],{"skillNo":62,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M7A3KYDK38Z8P032RX1HJ1ZB","https:\u002F\u002Fgithub.com\u002Feovipmak\u002Fcrowdsec-ui\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ffeature-development-planner\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M7A3KR8390H0E86SEGN2HD1W","crowdsec","Use when the user is installing, configuring, operating, or debugging CrowdSec — including cscli, LAPI\u002FCAPI, hub collections, parsers\u002Fscenarios\u002Fwhitelists deployment, bouncers (firewall, nginx, traefik, caddy), WAF (AppSec component) deployment, profiles, notifications, upgrades, and fail2ban migration. Covers bare-metal\u002Fsystemd, Docker, Kubernetes\u002FHelm, and CrowdSec Console enrollment. This is an operational skill — it does not author WAF rules, scenarios, or parsers.","https:\u002F\u002Fgithub.com\u002Feovipmak\u002Fcrowdsec-ui\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fcrowdsec\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M7A3KN3P65FF6R6R2N31X53F","wizard","Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.","https:\u002F\u002Fgithub.com\u002Feovipmak\u002Fcrowdsec-ui\u002Fblob\u002Fmain\u002F.commandcode\u002Fskills\u002Fwizard\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7A3KJYA8MZHTNJ4RM0C653H","triage","Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.","https:\u002F\u002Fgithub.com\u002Feovipmak\u002Fcrowdsec-ui\u002Fblob\u002Fmain\u002F.commandcode\u002Fskills\u002Ftriage\u002FSKILL.md",[],[]]