J
jpchauny/claude-plugins
Claude Code plugin marketplace: shared skills for the team
View on GitHub ↗Link checked 2026-11-12 · HTTP 200 · redirects to github.com
- Star count
- 0 ★ · jpchauny/claude-plugins · read from the repository page · (checked 2026-11-13 20:00:50)
- Source
- read directly from its GitHub page · type: open-source project
- Harvest history
- first seen 2026-10-25 · last seen 2026-11-14 · seen 24× · listed by 2 sources
- Score
- score 203 · 2 sources · repo
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: 开源项目. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
jpchauny/claude-plugins;first catalogued 2026-10-25;last seen 2026-11-14。There is no official certification or quality rating here — we record sources and dates only.# Indra Software Factory
以下摘录自该仓库的 README(片段) · 在 GitHub 读完整 README →
A Claude Code app, published as the plugin marketplace jpchauny-plugins, for
working in four layers: draft specs and specs written by people, norms and
derived norms generated from them, code built from the norms and the derived norms by agents.
The repository is a marketplace of apps, built from specs at four levels:
marketplace, app, module and use case, each with its folder specs/. The
marketplace is in specs/marketplace.md, how an app is
developed in specs/development.md, and this app in
apps/indra-software-factory/specs/app.md.
| Module (plugin) | Use cases |
| development-methodology | None: it gives every session an index of the development methodology (the four layers, the flow, their terms) |
| project-management | Create a project (/project-management:create-project) |
| specs-management | Recommend improvements to the specs (/specs-management:audit) |
| norms-management | Regenerate the norms (/norms-management:build, /norms-management:verify) |
| code-implementation | Implement the changed norms (not yet built) |
| drift-management | Report a drift (not yet built) |
| workflow-orchestration | Run the flow (not yet built) |
| utilities | Explore (/utilities:explore); the issue tree (/utilities:issue, /utilities:tree, /utilities:baseline); explain one step at a time (/utilities:explain); recap the session (/utilities:recap) |
Each module is a plugin of its own. A repository enables
development-methodology, utilities and the module of its layer
(APP-6).
## Install
Once per person:
sh
claude plugin marketplace add jpchauny/claude-plugins
claude plugin install project-management@jpchauny-plugins --scope user
Then, in any session, /project-management:create-project . It creates
the repositories of the four layers, each enabling in its .claude/settings.json
development-methodology, utilities and the module of its layer.
## Add the modules to an existing repository
In the repository (the commands write .claude/settings.json; commit it),
with the module of its layer: specs-management,
norms-management or code-implementation:
sh
claude plugin marketplace add jpchauny/claude-plugins --scope project
claude plugin install development-methodology@jpchauny-plugins --scope project
claude plugin install utilities@jpchauny-plugins --scope project
claude plugin install @jpchauny-plugins --scope project
### How utilities works
Root: an open issue labelled baseline (Línea de base YYYY-MM-DD), found from any repository that has pending items under it; nothing is configured. Its children are the top-level pending items; each bifurcation hangs under the node where it was found, across repositories.
Bifurcation: Claude proposes it in one line; nothing enters the tree without the user's yes. Every issue carries a hand-off: the context to resume it in any session.
State, from labels: question ⏳ waits for the user, blocked ⛔, breaks-ci 🔴, otherwise ▶ Claude can advance. Optional subject: tema: .
Seeing it: only on request (/utilities:tree): a summary and the tree in the chat. A page with the same view only when explicitly asked. Each person sees what their GitHub access allows.
working in four layers: draft specs and specs written by people, norms and
derived norms generated from them, code built from the norms and the derived norms by agents.
The repository is a marketplace of apps, built from specs at four levels:
marketplace, app, module and use case, each with its folder specs/. The
marketplace is in specs/marketplace.md, how an app is
developed in specs/development.md, and this app in
apps/indra-software-factory/specs/app.md.
| Module (plugin) | Use cases |
| development-methodology | None: it gives every session an index of the development methodology (the four layers, the flow, their terms) |
| project-management | Create a project (/project-management:create-project) |
| specs-management | Recommend improvements to the specs (/specs-management:audit) |
| norms-management | Regenerate the norms (/norms-management:build, /norms-management:verify) |
| code-implementation | Implement the changed norms (not yet built) |
| drift-management | Report a drift (not yet built) |
| workflow-orchestration | Run the flow (not yet built) |
| utilities | Explore (/utilities:explore); the issue tree (/utilities:issue, /utilities:tree, /utilities:baseline); explain one step at a time (/utilities:explain); recap the session (/utilities:recap) |
Each module is a plugin of its own. A repository enables
development-methodology, utilities and the module of its layer
(APP-6).
## Install
Once per person:
sh
claude plugin marketplace add jpchauny/claude-plugins
claude plugin install project-management@jpchauny-plugins --scope user
Then, in any session, /project-management:create-project . It creates
the repositories of the four layers, each enabling in its .claude/settings.json
development-methodology, utilities and the module of its layer.
## Add the modules to an existing repository
In the repository (the commands write .claude/settings.json; commit it),
with the module of its layer: specs-management,
norms-management or code-implementation:
sh
claude plugin marketplace add jpchauny/claude-plugins --scope project
claude plugin install development-methodology@jpchauny-plugins --scope project
claude plugin install utilities@jpchauny-plugins --scope project
claude plugin install @jpchauny-plugins --scope project
### How utilities works
Root: an open issue labelled baseline (Línea de base YYYY-MM-DD), found from any repository that has pending items under it; nothing is configured. Its children are the top-level pending items; each bifurcation hangs under the node where it was found, across repositories.
Bifurcation: Claude proposes it in one line; nothing enters the tree without the user's yes. Every issue carries a hand-off: the context to resume it in any session.
State, from labels: question ⏳ waits for the user, blocked ⛔, breaks-ci 🔴, otherwise ▶ Claude can advance. Optional subject: tema: .
Seeing it: only on request (/utilities:tree): a summary and the tree in the chat. A page with the same view only when explicitly asked. Each person sees what their GitHub access allows.
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/jpchauny-claude-plugins/)
- Source
- github · https://github.com/jpchauny/claude-plugins
- Browse by field
- Open source
- Listed by
- 2 independent sources
- added
- today
More like this
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.