Package the current skill collection into purpose-specific plugins

Start with the current skills/ layout, README.md, and CONTEXT.md, then check the Claude Code and Codex plugin manifest requirements and test npx skills add against a copy of the proposed layout. Decide where git_cleanup_adviser belongs and name the context plugin, then move skills, add manifests and marketplace files, and update links. Done means all four plugins install with only their own skills and the README commands work on a clean machine.

Problem

The repository contains 14 skills. Installation currently selects individual skills, and there are no plugin manifests or marketplace files. A person who wants issue workflows should be able to install those workflows without also installing Jérôme Étienne’s personal coding styles.

Package the collection into several plugins with clear purposes. The number of plugins and the final allocation need to be decided against the current inventory; the earlier four-plugin plan does not cover the current collection.

This issue replaces the earlier plan for one plugin at the repository root:

• https://github.com/jeromeetienne/coding_agent_plugin/issues/8

Current inventory

Reviewed on 9 November 2026. The skill inventory records thirteen current skills and one obsolete skill. The Rust style is ready for use. The dependency guide explains required dependencies and optional combinations.

The following table preserves the earlier grouping ideas while identifying decisions still needed. These are planning candidates, not newly approved plugin boundaries.

Dependencies to preserve

• issue_batch_workflow requires issue_fix_workflow and issue_creation.
• symbio_spec_to_docs requires symbio_spec, project Symbiospec data, and explicit documentation configuration.
• The obsolete docs_folder_agents_rules_system requires docs_folder_system. The dependency is not mutual.
• rules_of_the_repo selects applicable rule skills from a receiving project's rules list. Packaging must explain how those skills and their configurations are supplied; installing the complete collection is not automatically required.
• Optional combinations are not required installation dependencies. Do not claim that plugins have no dependencies on other plugins until the final allocation and instructions have been checked.

Open decisions

• Choose the final plugin boundaries, count, and names for all current skills.
• Choose the treatment of the obsolete skill without presenting the obsolete skill as recommended for new adoption.
• Decide how required dependencies are satisfied by each independently installed plugin.
• Decide whether to retain the existing individual-skill installation commands and source layout. Any replacement of those commands must be explicit and documented.
• Verify current Claude Code and Codex plugin formats, naming rules, installation commands, and skill command names before implementation. The original issue's examples are planning references, not live verification.

Proposed folder layout to verify

Use one folder per plugin if supported by the current tools. The earlier proposal used marketplace entries pointing at ./plugins/<plugin name>, with separate Claude Code and Codex manifests inside each plugin folder. Confirm the exact manifest locations and source fields against the current official documentation and real installed clients before adopting the layout:

• Claude Code plugin marketplaces
• Codex plugin building documentation

Do not move the authoritative skill folders until the installation compatibility test below establishes a workable layout.

Risk to prove first

The critical assumption is that the proposed layout can expose the intended skills through real Claude Code and Codex plugin installation while preserving the agreed individual-skill installation behavior.

Use an isolated test copy containing representative, nonempty skills and a real required dependency. Test the actual clients and installation routes, record raw output, and state exactly what each test proves. Manifest validation alone does not prove that skills load.

The current installation guide and README.md use npx skills add jeromeetienne/coding_agent_plugin, including individual selection with --skill. Test discovery and individual selection against the proposed layout before moving skills. If compatibility fails, decide the source layout or an explicitly approved installation change before proceeding. Avoid maintaining divergent authoritative copies.

Tasks

• Confirm the complete inventory and actual dependencies from the current skill instructions.
• Agree the plugin boundaries, names, dependency handling, and obsolete-skill treatment.
• Verify the current tool formats and prove the proposed layout with the smallest real installation tests.
• Add the agreed plugin manifests and marketplace entries, and move skill folders only if the verified layout requires movement.
• Run the validation commands supported by the installed Claude Code and Codex versions.
• Install every plugin independently in real Claude Code and Codex clients; inspect the loaded skill lists and exercise representative instructions, including required dependencies.
• Verify individual-skill discovery and selection with npx skills add, or document the explicitly approved replacement.
• Update README.md, the installation guide, the skill inventory, and the dependency guide.
• Update CONTEXT.md, receiving-project examples in AGENTS.md where affected, and all references to moved skills. Apply the repository rules for any new folder context files.
• Check repository links and the published documentation affected by layout or installation changes.

Acceptance

• Every current skill has an explicit packaging decision; the obsolete skill has an explicit compatibility decision.
• Each agreed plugin installs independently in Claude Code and Codex and exposes exactly the intended skills, with required dependencies available and documented.
• Installing workflow plugins does not install personal coding styles unless explicitly selected.
• The documented installation commands work in clean, isolated environments. Report the client versions, actual commands, raw results, and any untested environment limits.
• No repository link points to a removed path, and installation and dependency documentation match the implemented layout.
• Validation, installation, skill loading, and representative execution are reported separately; passing one check does not imply the others passed.