Design software features and architectures, then produce an implementation-ready plan handoff.
npx skills add https://github.com/nebius/nebius-ps-services --skill design-nebius
Please help me install this Agent Skill. Skill: design Source: https://github.com/nebius/nebius-ps-services/tree/main/skills/design Command: npx skills add https://github.com/nebius/nebius-ps-services --skill design-nebius
/plan handoff. - Scoped specialist delegation: Routes technology due diligence to research, application-stack choices to app-stack, AI subsystem behavior and policy to ai-agent-design, AI component selection to ai-stack, and checklist review to system-design-rules without reopening fixed decisions. - AI capability classification: Classifies every AI-enabled capability as deterministic code, a direct model call, a deterministic workflow, or an agent, following the principle of deterministic where possible and agentic where necessary. - Use Case: You need to add a new API-backed feature to an existing service. The skill inspects the repository, confirms the fixed stack, designs a vertical end-to-end slice, compares alternatives, and emits a /plan handoff another session can implement directly. ## Quick Start Ask the agent to use the design skill to turn your feature request into an evidence-backed design and implementation plan before any code is written.High-intent search queries and answers about installing and using this skill.
Invoke the design skill with your requirements and constraints. It inspects the existing system, researches unfamiliar technologies, designs components and boundaries, compares alternatives, and produces a /plan handoff ready for implementation.
The skill classifies each AI capability using a decision tree: deterministic code when no model judgment is needed, a direct call when one request suffices, a deterministic workflow when code owns the steps, and an agent only when the model must choose actions or next steps.
Use design when the causal mechanism is already proven and the remediation changes architecture, interfaces, data ownership, or cross-component workflows. Use troubleshoot when the failure mechanism is unknown or the repair stays inside one existing private boundary.
No. It never writes production code, tests, migrations, or scaffolding. It ends with a /plan handoff, and may optionally emit a one-way scaffold handoff for an explicit scaffold-project invocation after design approval.
Yes. After confirming no relevant source exists, it skips codebase discovery and designs from requirements, research-backed technology choices, and the intended deployment context, naming the initial project structure and bootstrap order.
MysMonExtract goals, constraints, and success criteria through structured interview phases.
trevorbyrumOrchestrate multi-phase project initialization from scaffolding to approved build plans.
yeeder0520Design scalable system architectures and select technology stacks.
tomzxCreate missing .sdlc/ directories and copy default templates without overwriting existing files.