Claude Skill

spinoff

Spin a requirement group off into its own project (principal's explicit decision only)

LLM Mart · 0 points · 2 views 0 listing impressions 0 install-command copies
Download pche-broken-artist-forge-of-thought-.claude_skills_spinoff-3ef759b.zip · 1 KB

Install

skills CLI npx skills add https://github.com/pche-broken-artist/forge-of-thought/tree/main/.claude/skills/spinoff
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install pche-broken-artist-forge-of-thought@llmmart
Git git clone https://github.com/pche-broken-artist/forge-of-thought.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole pche-broken-artist/forge-of-thought collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Execute only on the principal's explicit instruction — never propose-and- run in one step (CLAUDE.md, Spin-off rule).

  1. Confirm scope with the principal: list the items (REQ/OOS/CON/ASM/DEL/TBC/SCR) of group "$1" in project $0 that will move. He may adjust the list.
  2. Create projects/$2/ by the /new-project procedure (kind thought) — files only, no git: the new project's repository and remote are the principal's one-off act afterwards (CLAUDE.md, Persistence).
  3. Derive projects/$2/00-brief.md from the relevant parts of the source 10-intent.md: a short brief, in the language settled at step 2, capturing why this became its own project and what it inherits. This brief is derived by Claude: present it to the principal as a draft and, on his word, approve it through the /forge brief procedure (.claude/skills/forge/states/brief.md, its Course).
  4. Mine the brief into the new project's intent through the /forge intent procedure (.claude/skills/forge/states/intent.md, its Course), which creates 10-intent.md and writes the brief's mining record in the intent's history (templates/history.md).
  5. In the source project, intent-first (CLAUDE.md, Working methods): record the spin-off in the source intent through the /forge intent procedure (the group's substance is now delivered by project $2), then derive the change in the source assignment through the /forge assignment procedure, which marks the moved items superseded (never deleted) and replaces the group with one link item — "REQ.NNNN: Delivered by project $2, see its assignment." This command itself writes only the DEC in decisions.md (the shape of a record: templates/decisions.md).
  6. Remake both ledgers, python scripts/forge-ledger.py <slug> for each, and report the result.
Files (forge-of-thought)
  • SKILL.md 2 KB
    ---
    description: Spin a requirement group off into its own project (principal's explicit decision only)
    argument-hint: "<source-project> <group-name> <new-slug>"
    disable-model-invocation: true
    ---
    
    Execute only on the principal's explicit instruction — never propose-and-
    run in one step (CLAUDE.md, Spin-off rule).
    
    1. Confirm scope with the principal: list the items
       (REQ/OOS/CON/ASM/DEL/TBC/SCR)
       of group "$1" in project $0 that will move. He may adjust the list.
    2. Create `projects/$2/` by the `/new-project` procedure (kind
       `thought`) — files only, no git: the new project's repository and
       remote are the principal's one-off act afterwards (CLAUDE.md,
       Persistence).
    3. Derive `projects/$2/00-brief.md` from the relevant parts of the
       source 10-intent.md: a short brief, in the language settled at
       step 2, capturing why this became its own project and what it
       inherits. This brief is derived by Claude: present it to the
       principal as a draft and, on his word, approve it through the
       `/forge brief` procedure
       (`.claude/skills/forge/states/brief.md`, its Course).
    4. Mine the brief into the new project's intent through the
       `/forge intent` procedure
       (`.claude/skills/forge/states/intent.md`, its Course), which
       creates 10-intent.md and writes the brief's mining record in the
       intent's history (`templates/history.md`).
    5. In the source project, intent-first (CLAUDE.md, Working methods):
       record the spin-off in the source intent through the `/forge
       intent` procedure (the group's substance is now delivered by
       project *$2*), then derive the change in the source assignment
       through the `/forge assignment` procedure, which marks the moved
       items superseded (never deleted) and replaces the group with one
       link item — "REQ.NNNN: Delivered by project *$2*, see its
       assignment." This command itself writes only the DEC in
       decisions.md (the shape of a record: `templates/decisions.md`).
    6. Remake both ledgers, `python scripts/forge-ledger.py <slug>` for
       each, and report the result.
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.