apply

Translate OpenSpec change plans into executable subagent instructions.

9|9|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/nullmastermind/viber-router --skill apply-nullmastermind
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: apply
Source: https://github.com/nullmastermind/viber-router/tree/main/.claude/skills/apply
Command: npx skills add https://github.com/nullmastermind/viber-router --skill apply-nullmastermind

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns conversation plans or OpenSpec changes into actionable implementation steps and launches a subagent to carry out or continue development work, reducing friction when moving from planning to execution.

Core Features & Use Cases

  • Context gathering: Assemble context automatically from an OpenSpec change name or from a conversation plan so the implementation agent has relevant artifacts and summaries.
  • Decision translation: Convert key decisions, requirements, and scope into structured instructions the subagent can execute.
  • Agent orchestration: Brief the user and launch a subagent configured for apply workflows, suitable for starting implementations, continuing development, or executing task lists derived from brainstorming.

Quick Start

Launch the apply skill with a change name or a concise plan summary and request execution of the implementation tasks.

Frequently Asked Questions about apply

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn a conversation plan into executable development tasks?

To turn a conversation plan into executable development tasks, the Skill gathers relevant context and key decisions, translating them into structured subagent instructions for immediate execution.

What is the best way to implement OpenSpec changes automatically?

Implementing OpenSpec changes automatically is done by passing a change name to assemble relevant artifacts and summaries, which then launches a configured subagent to carry out the development workflow.

How do I translate brainstorming decisions into concrete task lists?

Translating brainstorming decisions into concrete task lists involves converting key decisions, requirements, and scope into structured instructions that a subagent can directly execute.

Can I continue an interrupted development workflow from a previous spec?

You can continue an interrupted development workflow from a previous spec by supplying the original change name or summarized plan, which collects prior context and resumes execution via a subagent.

Do I need an existing OpenSpec change to start implementation workflows?

You do not need an existing OpenSpec change to start implementation workflows; you can supply a summarized conversation plan instead, which the Skill uses to gather context and launch the subagent.