skill_plan

Plan APC plugin architecture and DSP strategy with implementation milestones.

3|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/joshband/LocusQ --skill skill-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill_plan
Source: https://github.com/joshband/LocusQ/tree/main/.codex/skills/plan
Command: npx skills add https://github.com/joshband/LocusQ --skill skill-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning and structuring DSP plugin architectures, enabling repeatable, well-scoped development milestones.

Core Features & Use Cases

  • Defining architecture components, DSP processing chains, and implementation milestones for APC plugins.
  • Generating implementation roadmaps and phase plans aligned with DREAM and PLAN activities.
  • Providing artifact templates (architecture.md, plan.md) and progress tracking via status.json.

Quick Start

Plan the DSP architecture for a new APC plugin by outlining the core components and milestones in one sentence.

Frequently Asked Questions about skill_plan

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

FAQPage Schema
How do I plan DSP architecture for a plugin project?

To plan DSP architecture for a plugin, outline the core components, processing chains, and implementation milestones. This approach generates architectural artifacts and roadmaps to ensure well-scoped, repeatable development.

What is the best way to structure implementation milestones for an audio plugin?

The best way to structure implementation milestones for an audio plugin is to align them with DREAM and PLAN activities, using input specifications to generate a structured phase plan and track progress via status.json.

Can I use creative briefs and parameter specs to generate a project roadmap?

Yes, you can use creative briefs and parameter specs as inputs to generate a project roadmap. The planning process reads these files to produce architectural artifacts and update the project's phase history.

Does this DSP planning approach require specific framework choices upfront?

No, specific framework choices are not required upfront. The planning process helps you determine and record framework choices, complexity metrics, and phase history directly into a status.json file during the architectural planning phase.

What artifacts do I need to document a DSP plugin architecture?

To document a DSP plugin architecture, you need an architecture.md file for component definitions and a plan.md file for roadmaps. These artifacts provide structured templates for defining processing chains and tracking milestones.

Why should I outline architecture before developing DSP plugins?

You should outline architecture before developing DSP plugins to solve the problem of unstructured development. Defining components and milestones early enables repeatable, well-scoped execution and prevents scope creep.