echoVic/boss-skill

Architecture Design defines system architecture choices, layering, directory structure, data models, and API design. Use it when turning research results into a concrete project architecture document.

Backend API Development covers RESTful and GraphQL API design, request validation, error handling, and security practices. Use it when implementing backend endpoints that must follow a defined API contract.

Backend Testing Guide explains how to write unit, integration, and E2E tests for backend code. Use it when you need test coverage for services, API endpoints, database behavior, and full request flows.

Boss 编排从需求到部署的多 Agent 研发流水线，包含事件溯源、不可绕过门禁和确定性评估。适合启动新项目、交付新功能，或对现有项目做规划、评审、测试和发布。

Brainstorming turns a vague idea into a structured design brief by asking business-focused questions. Use it when a user says things like "I want to build..." but the need is not yet clear.

Changelog Generation automatically builds or appends release notes from git commit history and pipeline artifacts. Use it after deployment or before a release to summarize changes in Keep a Changelog format.

Code Review provides a checklist and best practices for reviewing code changes. Use it to check correctness, quality, security, performance, and maintainability before merging.

Competitive Analysis helps you compare direct, indirect, and emerging competitors across features, UX, users, business, and technology. Use it during product planning or iteration to find gaps and differentiation opportunities.

Data API Design covers ERD modeling, data dictionaries, and RESTful API conventions for system architecture work. Use it when defining tables, relationships, request/response formats, and auth rules.

Deployment Process covers deployment strategies, CI/CD steps, and environment setup for reliable releases. Use it when configuring builds, tests, and rollout workflows from development to production.

Frontend Component Development covers component design, state management, styling, accessibility, performance, APIs, and testing for building frontend UI. Use it when implementing or reviewing reusable components and related flows.

Frontend Testing Guide explains how to write unit, integration, and E2E tests for frontend components, hooks, forms, and user flows. It is used when building or reviewing frontend test coverage and test structure.

Monitoring and Alerting defines metrics, thresholds, and notification rules to keep systems stable. Use it when setting up error, latency, resource, and log-based alerts.

PRD Writing defines a standard structure for product requirements documents so teams can produce complete, clear, and executable PRDs. Use it after discovery and analysis when design, development, and testing need a shared spec.

Playwright E2E Testing covers initialization, Page Object Models, auth reuse, API mocks, visual regression, multi-browser runs, CI integration, and debugging. Use it to automate end-to-end verification of key web flows.

Requirement Penetration helps unpack a user's stated request into explicit, implicit, latent, and delight needs using 5W2H questioning and prioritization. Use it when drafting or refining PRDs and product requirements.

Risk Assessment identifies project risks and maps them to response strategies. Use it when you need to evaluate technical, resource, requirement, or dependency risks and decide how to handle them.

Strategic Review evaluates a feature or project from a CEO-level business perspective. Use it to judge market fit, ROI, competitive advantage, risk, and alignment before deciding whether to proceed.

Task Breakdown breaks requirements into small, executable development tasks using WBS and SMART criteria. Use it when planning work, estimating effort, or organizing dependencies.

Tech Research guides systematic investigation and comparison of technology options before architecture design or stack selection. It is used to gather evidence, evaluate tradeoffs, and produce a recommendation backed by data.

Tech Stack Detection analyzes project config files to identify languages, frameworks, databases, testing tools, and deployment setup. Use it before code generation or architecture work to match the existing stack.

Technical Standards defines naming, code organization, error handling, and test expectations for consistent TypeScript code. Use it when setting team conventions or reviewing code quality.

Test Execution detects a project’s test framework, runs unit, integration, or E2E tests, and parses the results. Use it when you need to verify changes with real test output and coverage.

Test Strategy defines the test pyramid and coverage expectations for unit, integration, and E2E tests. It is used to plan QA coverage, verify core user paths, and check security and performance basics.

User Research helps define target users with personas, journey maps, and usage scenarios. Use it when planning a product or PRD and you need to understand user needs, behaviors, and pain points.