Skip to content

feat: package Nous as a Claude Code plugin with skills and slash commands #125

@sriumcp

Description

@sriumcp

TL;DR

Ship Nous as a Claude Code plugin. Expose campaign verbs as skills (/nous-run, /nous-status, /nous-resume, /nous-list, /nous-bisect, /nous-find-principle). Discoverable from the /<tab> palette in any Claude Code session.

Why this matters

Today users invoke Nous via nous run … from a separate terminal. Inside a Claude Code session you cannot easily say "run the saturation campaign and watch it"; you have to context-switch out. Plugins solve this — they're the canonical Claude Code distribution mechanism for reusable team workflows.

What's already shipped

Proposed approach

  1. Create plugin/nous/plugin.json with metadata.
  2. Create plugin/nous/skills/ with one markdown file per skill:
  3. Add a claude plugin install nous story (publish to a registry or document local install).
  4. Skills should accept conversational arguments where possible ("status of best-of-field" should work, not just "status best-of-field").

Acceptance criteria

  • After claude plugin install ./plugin/nous, /nous-<tab> lists at least 5 skills.
  • Each skill works end-to-end on a real campaign.
  • Documentation walks a newcomer through install and first use.

Out of scope


Part of #120.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions