J
jpchauny/claude-plugins
Claude Code plugin marketplace: shared skills for the team
在 GitHub 查看 ↗链接已于 2026-11-12 核查 · HTTP 200 · 最终跳转到 github.com
- ★ 数取值
- 0 ★ · jpchauny/claude-plugins · 取自该仓库的 GitHub 页面 · (2026-11-13 20:00:50 核对)
- 来源明细
- 从该仓库的 GitHub 页面直接读取 · 条目类型:开源项目
- 收录与活跃
- 收录于 2026-10-25 · 最近见到 2026-11-14 · 共见到 24 次 · 被 2 个来源列出
- 评分构成
- 综合分 203 · 2 个来源 · repo
常见问题(答案都来自我们的记录)
它适合谁 / 用来做什么?
我们把它归在这些标签下: 开源项目。标签来自条目自身,不是我们强加的分类。
谁维护它、还在更新吗?
仓库
jpchauny/claude-plugins;我们收录于 2026-10-25;最近见到 2026-11-14。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。# 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.
收录徽章(可选)
想把收录标记放进 README 就复制这行,可选,不影响收录。
[](https://anclum.com/zh/s/jpchauny-claude-plugins/)
- 来源
- github · https://github.com/jpchauny/claude-plugins
- 按领域浏览
- 开源项目
- 收录来源
- 2 个独立来源
- 收录于
- 今天
同类推荐
所属领域与标签
每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。