Claude Skill

forge

Work the document chain — bare = state map, with a target = iterate that artefact

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

Install

skills CLI npx skills add https://github.com/pche-broken-artist/forge-of-thought/tree/main/.claude/skills/forge
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

Role: dispatcher for work on the document chain. The chain is a star, not a fixed line: each target state declares its own inputs in its definition file; where the definitions live and how the chain grows is CLAUDE.md, Document chain's. This dispatcher never changes.

Bare /forge — report the map.

  1. Infer the current project from context ($0 may be a slug; if ambiguous, ask).
  2. Make the project's ledger, python scripts/forge-ledger.py <slug> (the ledger is made at read time, SOL.0680; a project of the shape before the migration is said as templates/project.md says), read it and list .claude/skills/forge/states/ for the available target states.
  3. Report compactly:
    • the project's kind and language (the project file, POS.1590, POS.0960) and whether it is under git — as python scripts/forge-status.py --remote of step 4 reports it, a repository of its own or "not under git" (POS.0550), stated as a fact, never as a defect (CLAUDE.md, Persistence);
    • a library is material, not a project waiting for a brief: report its sources and research (from the ledger and the indexes) and stop after the git line — no chain, no target states, no next step beyond /ingest;
    • which chain artefacts exist, at what version and status — briefs with their mining state, a draft brief or a pending / partial one named as work waiting; a layer the project does not have is not reported as missing (CLAUDE.md, Ledger);
    • which target states can be worked on from here (inputs exist) and which cannot yet (say what is missing);
    • which renders are stale (as /render step 5 defines it) and which published files are (state stale in the ledger's Published table);
    • which libraries the project needs (the ledger's Dependencies table, POS.1020) and whether each is cloned alongside;
    • what is waiting on the principal (from the ledger): the few live matters named in words, the ID in brackets as an address, the rest as a count (CLAUDE.md, Working methods, Plain speech).
  4. Recommend the natural next step in words — a recommendation, never a gate — and, where the map lists more than one matter waiting on the principal, offer a walkthrough of them (CLAUDE.md, Working methods).
  5. End with the state of the engine and of the project against the origin, from python scripts/forge-status.py --remote, as the map's last word (POS.1710): said as a fact with the words of POS.1490 (up to date, behind, ahead, diverged, no origin) and with that state's one offer, as /pull step 1 has it; the map says it looked at the remote and runs none of it.

/forge <state> — work on that artefact.

  1. Resolve .claude/skills/forge/states/$0.md. If it does not exist, list the states that do and stop. On a library, which has no chain (CLAUDE.md, Document chain), say so and stop: no state is worked there.
  2. Read the file and follow it. It declares the target artefact, its inputs and its working rules; everything else (write-once-per-round, versioning, ledger upkeep) follows the core conventions. A state file's arguments are those following the state name: for brief the name, then the slug; for the other states the slug.
Files (forge-of-thought)
  • states
    • assignment.md 6.7 KB
      Loading…
    • brd.md 12.4 KB
      Loading…
    • brief.md 8.3 KB
      Loading…
    • intent.md 6.1 KB
      Loading…
    • solution-design.md 5.4 KB
      Loading…
  • SKILL.md 3.4 KB
    ---
    description: Work the document chain — bare = state map, with a target = iterate that artefact
    argument-hint: "[target-state] [project-slug]"
    ---
    
    Role: dispatcher for work on the document chain. The chain is a star,
    not a fixed line: each target state declares its own inputs in its
    definition file; where the definitions live and how the chain grows
    is CLAUDE.md, Document chain's. This dispatcher never changes.
    
    **Bare `/forge` — report the map.**
    1. Infer the current project from context ($0 may be a slug; if
       ambiguous, ask).
    2. Make the project's ledger, `python scripts/forge-ledger.py <slug>`
       (the ledger is made at read time, SOL.0680; a project of the shape
       before the migration is said as `templates/project.md` says), read it and
       list `.claude/skills/forge/states/` for the available target states.
    3. Report compactly:
       - the project's kind and language (the project file, POS.1590,
         POS.0960) and whether it is
         under git — as `python scripts/forge-status.py --remote` of step
         4 reports it, a repository of its own or "not under git"
         (POS.0550),
         stated as a fact, never as a defect (CLAUDE.md, Persistence);
       - a `library` is material, not a project waiting for a brief:
         report its sources and research (from the ledger and the
         indexes) and stop after the git line — no chain, no target
         states, no next step beyond `/ingest`;
       - which chain artefacts exist, at what version and status —
         briefs with their mining state, a draft brief or a `pending` /
         `partial` one named as work waiting; a layer the project does
         not have is not reported as missing (CLAUDE.md, Ledger);
       - which target states can be worked on from here (inputs exist) and
         which cannot yet (say what is missing);
       - which renders are stale (as `/render` step 5 defines it) and
         which published files are (state `stale` in the ledger's
         Published table);
       - which libraries the project needs (the ledger's Dependencies
         table, POS.1020) and whether each is cloned alongside;
       - what is waiting on the principal (from the ledger): the few live
         matters named in words, the ID in brackets as an address, the
         rest as a count (CLAUDE.md, Working methods, Plain speech).
    4. Recommend the natural next step in words — a recommendation, never a
       gate — and, where the map lists more than one matter waiting on
       the principal, offer a walkthrough of them (CLAUDE.md, Working
       methods).
    5. End with the state of the engine and of the project against the
       origin, from `python scripts/forge-status.py --remote`, as the
       map's last word (POS.1710): said as a fact with the words of
       POS.1490 (up to date, behind, ahead, diverged, no origin) and with
       that state's one offer, as `/pull` step 1 has it; the map says it
       looked at the remote and runs none of it.
    
    **`/forge <state>` — work on that artefact.**
    1. Resolve `.claude/skills/forge/states/$0.md`. If it does not exist, list
       the states that do and stop. On a `library`, which has no chain
       (CLAUDE.md, Document chain), say so and stop: no state is worked
       there.
    2. Read the file and follow it. It declares the target artefact, its
       inputs and its working rules; everything else (write-once-per-round,
       versioning, ledger upkeep) follows the core conventions. A state
       file's arguments are those following the state name: for `brief`
       the name, then the slug; for the other states the slug.
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.