Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
30 changes: 3 additions & 27 deletions .agents/plugins/marketplace.json
Original file line number Diff line number Diff line change
@@ -1,44 +1,20 @@
{
"name": "conceptadev",
"interface": {
"displayName": "Conceptadev"
"displayName": "Bitwild"
},
"plugins": [
{
"name": "product-kit",
"name": "bitwild-team-kit",
"source": {
"source": "local",
"path": "./plugins/product-kit"
},
"policy": {
"installation": "AVAILABLE",
"authentication": "ON_INSTALL"
},
"category": "Productivity"
},
{
"name": "engineering-kit",
"source": {
"source": "local",
"path": "./plugins/engineering-kit"
"path": "./plugins/bitwild-team-kit"
},
"policy": {
"installation": "AVAILABLE",
"authentication": "ON_INSTALL"
},
"category": "Coding"
},
{
"name": "design-kit",
"source": {
"source": "local",
"path": "./plugins/design-kit"
},
"policy": {
"installation": "AVAILABLE",
"authentication": "ON_INSTALL"
},
"category": "Productivity"
}
]
}
19 changes: 5 additions & 14 deletions .claude-plugin/marketplace.json
Original file line number Diff line number Diff line change
@@ -1,24 +1,15 @@
{
"name": "conceptadev",
"owner": {
"name": "Concepta",
"name": "Bitwild",
"url": "/btwld"
},
"plugins": [
{
"name": "product-kit",
"source": "./plugins/product-kit",
"description": "Product exploration, evidence synthesis, competitive and friction research, structured PRDs, and connected WBS planning."
},
{
"name": "engineering-kit",
"source": "./plugins/engineering-kit",
"description": "Engineering architecture, implementation planning, unified code and structural review, PR and CI workflows, business rules, and falsifiable verification."
},
{
"name": "design-kit",
"source": "./plugins/design-kit"
"name": "bitwild-team-kit",
"source": "./plugins/bitwild-team-kit",
"description": "Plan product delivery, design interfaces, write documentation, review engineering changes, and build with Dart and Flutter."
}
],
"description": "Private Concepta plugins for product and engineering workflows."
"description": "Plan product delivery, design interfaces, write documentation, review engineering changes, and build with Dart and Flutter."
}
53 changes: 22 additions & 31 deletions AGENTS.md
Original file line number Diff line number Diff line change
@@ -1,38 +1,29 @@
# Agent Plugins
# Bitwild Team Kit

This repository owns Concepta's Product, Engineering, and Design kits for Codex
and Claude Code. Maintain these kits directly; do not introduce upstream skill
tracking, import/merge workflows, or synchronization with another skills repository.
Maintain one team plugin for Codex and Claude Code. Its canonical files live under
`plugins/bitwild-team-kit/`. Both marketplace entries point to that directory.
Keep skill names unique and resolve runtime resources relative to the loaded skill.
Keep prior releases in Git.

## Ownership
## Workflow ownership

- Product Kit owns exploration, research, PRDs, requirements/questions, and WBS.
Reuse its record contract rather than duplicating requirements or resolutions.
- Engineering Kit owns technical decisions, implementation plans and execution,
specialized reviews, business-rule modeling, and verification. Keep delivery
breakdowns distinct from implementation plans; no automatic handoff is required.
- Design Kit owns interface design, critique, accessibility, UX copy, and study planning.
Product Kit owns research synthesis; Engineering Kit owns functional verification.
- Dart/Flutter is an external official plugin managed by the client. Keep its
skills and MCP configuration out of these kits; see docs/external-plugins.md.
Choose the workflow that matches the requested deliverable. Product requirements,
questions, and decisions share one source. Delivery breakdowns assign work to
packages. Engineering plans describe implementation. Design research planning
and analysis of collected evidence are separate tasks. Use Writing for Humans
for documents people act on, Writing for Agents for agent instructions, and
Deep Code Review for final review. Preserve explicit invocation policies.

## Author and maintain
Keep package-specific guidance aligned with the project's resolved dependency.
Link to upstream package guides for detail. General Dart and Flutter skills and
Dart MCP come from Flutter's official provider.

- Canonical content lives in `plugins/<kit>/`. Resolve helpers and resources from
the loaded skill's location. Do not edit installed caches or duplicate bundles.
- Use Skill Creator for skill changes and provider guidance for packaging. Give
each skill a clear outcome; add components only when they serve a concrete use.
- Preserve user scope, authoritative IDs, and the distinction between evidence,
proposals, decisions, and implementation proof. JSON schemas define structured
records; Word/PDF references define presentation.
- Retain source attribution and license notices. `SOURCES.md` is informational,
not an instruction to fetch, compare, or merge external repositories.
- Keep project evidence and generated deliverables outside plugin packages.
Preserve unrelated files and active plugin installations.
## Author and validate

## Validate and release
Use Skill Creator for changes to a skill. Preserve source attribution, license
notices, schema and reference contracts, and existing user work. Keep client
records and generated output outside the plugin. Use fictional test fixtures.

Keep both catalogs and both provider manifests aligned. Run the README checks and
focused validation for changed behavior. Separate structural validation from
behavioral evaluation; do not report fixtures as executed tests. Use semantic
versions and plugin-scoped release tags. Preserve prior releases in Git.
Run the checks in README.md, verify resource paths in an isolated installed
copy, and test changed workflows. Keep the provider manifests and catalog
aligned. Record what ran separately from model discovery or behavior claims.
81 changes: 20 additions & 61 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,87 +1,46 @@
# Concepta Agent Plugins
# Bitwild Team Kit

Plugins for Codex and Claude Code. Maintain skills directly in this
repository; there is no upstream import, tracking, or merge workflow.

## Kits

| Plugin | Purpose | Skills | Version |
| --- | --- | --- | --- |
| [Product Kit](plugins/product-kit/README.md) | Research, requirements, PRDs, and delivery breakdowns | 6 | 0.3.2 |
| [Engineering Kit](plugins/engineering-kit/README.md) | Technical decisions, implementation, reviews, PR/CI workflows, writing, and verification | 16 | 0.2.0 |
| [Design Kit](plugins/design-kit/README.md) | Interface design, critique, accessibility, UX copy, and research planning | 10 | 0.1.1 |

Product Kit owns the shared requirements, questions, and decisions. Engineering
Kit turns settled scope into implementation work without creating a second
requirement baseline. Use the skill that matches the task; no automatic sequence
or handoff is required.

A [flattened source snapshot](agent-plugins.flattened.md) is available for review.
Binary assets are listed by hash; install plugins from their folders, not the snapshot.
One plugin for Bitwild's product, design, engineering, and specialist Dart and Flutter workflows. Pick the task you need: define a requirement, break work into delivery packages, design an interface, write for people or agents, or give a change its final code review. [Browse the team workflows](plugins/bitwild-team-kit/README.md)

## Install

Clone or register this repository. Install the kits in the client you use.
The GitHub repository is `btwld/agent-plugins`. Its marketplace ID is `conceptadev`; the installable plugin is `bitwild-team-kit`.

### Codex
**Codex**

```sh
codex plugin marketplace add https://github.com/btwld/agent-plugins.git
codex plugin add product-kit@conceptadev
codex plugin add engineering-kit@conceptadev
codex plugin add design-kit@conceptadev
codex plugin add bitwild-team-kit@conceptadev
```

### Claude Code
**Claude Code**

```sh
claude plugin marketplace add https://github.com/btwld/agent-plugins.git
claude plugin install product-kit@conceptadev
claude plugin install engineering-kit@conceptadev
claude plugin install design-kit@conceptadev
claude plugin install bitwild-team-kit@conceptadev
```

Start a new session afterward. In Codex, request the relevant skill. Claude
commands include `/product-kit:write-prd`, `/product-kit:write-wbs`, and
`/engineering-kit:writing-plans`. Use one active provider for each plugin namespace;
cloning or maintaining this repository does not replace installed plugins.
Open a fresh session. Try `$deep-code-review` in Codex or `/bitwild-team-kit:deep-code-review` in Claude Code. For ACK schemas, Noir terminal apps, Mix styling, or Remix components, invoke `ack`, `noir`, `mix`, or `remix-flutter` under the same plugin.

Dart/Flutter uses a separate official provider. See [Dart/Flutter setup](docs/external-plugins.md).
Neither kit duplicates its skills or MCP server.
**Working on Dart or Flutter?** From a checkout of this repository, run `./scripts/install-with-flutter.sh codex` or `./scripts/install-with-flutter.sh claude` to install both the team kit and Flutter’s official plugin. Flutter supplies the general SDK skills and Dart MCP. If you already have the team kit, invoke `$flutter-setup` in Codex or `/bitwild-team-kit:flutter-setup` in Claude Code to check or configure Flutter on the target machine. [Official Dart and Flutter setup](docs/external-plugins.md)

## Maintain
## Switch from the previous kits

Canonical content lives in `plugins/<kit>/skills/<skill>/`. Templates, scripts,
references, and fixtures stay inside their owning plugin so cached installations
remain portable. Codex and Claude share the same content:

- `.agents/plugins/marketplace.json`: Codex catalog.
- `.claude-plugin/marketplace.json`: Claude catalog.
- `plugins/<kit>/.codex-plugin/plugin.json`: Codex plugin metadata.
- `plugins/<kit>/.claude-plugin/plugin.json`: Claude plugin metadata.

Keep each kit's version identical in both manifests and use scoped release tags
such as `product-kit/v0.3.2`. Keep development cachebusters out of releases.
Source attribution and license notices are in each kit's `SOURCES.md`; they do
not define a maintenance workflow. Keep real project records and generated output
outside the plugins. Bundled examples are fictional.
1. If `conceptadev` is already registered, refresh it with `codex plugin marketplace upgrade conceptadev` or `claude plugin marketplace update conceptadev`.
2. Install `bitwild-team-kit@conceptadev`. Check that the new plugin lists the skills you use.
3. Remove the former company kits you installed: `engineering-kit`, `product-kit`, `design-kit`, and `dart-package-kit`. For example, run `codex plugin remove engineering-kit@conceptadev` or `claude plugin uninstall engineering-kit@conceptadev` in its original scope. Open a fresh session.
4. Update saved Claude commands to the new prefix. For example, `/product-kit:write-wbs` becomes `/bitwild-team-kit:write-wbs`. Replace `pr-prep` with `pr-authoring` for branch preparation and `wild-code-review` with `deep-code-review` for final reviews. Scripts that used a checkout path should now resolve resources under `plugins/bitwild-team-kit/`.

## Validate

From the repository root:

```sh
uv run --with jsonschema==4.26.0 python -m unittest discover -s plugins/product-kit/scripts/tests
python3 -m unittest discover -s plugins/engineering-kit/tests
python3 -m unittest discover -s tests
claude plugin validate plugins/product-kit --strict
claude plugin validate plugins/engineering-kit --strict
claude plugin validate plugins/design-kit --strict
python3 -m unittest discover -s plugins/bitwild-team-kit/tests
uv run --with jsonschema==4.26.0 python -m unittest discover -s plugins/bitwild-team-kit/scripts/tests
claude plugin validate plugins/bitwild-team-kit --strict
claude plugin validate . --strict
```

Use Skill Creator for skill edits and provider validators for packaging changes.
Test changed helpers and check that resources resolve from an isolated plugin copy.
Included behavioral fixtures are not executed by these commands; passing helper
and packaging tests does not prove automatic skill selection or model behavior.
See each kit's guide for runtime dependencies and generation commands.
Both marketplaces load the same `plugins/bitwild-team-kit/` directory. Release its skills together by matching the version in both plugin manifests. For a new kit release, use Claude Code’s dependency-resolution tag format, for example `bitwild-team-kit--v1.0.0`. Each package workflow follows the Dart package version resolved by the consuming project. [Plugin release tags](https://code.claude.com/docs/en/plugins/dependencies#tag-plugin-releases-for-version-resolution)

The [older flattened snapshot](agent-plugins.flattened.md) records an earlier layout. [Source credits and licensing](plugins/bitwild-team-kit/SOURCES.md)
17 changes: 15 additions & 2 deletions docs/external-plugins.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,8 +3,9 @@
Use `dart-flutter@dart-flutter` from the official
[Flutter plugin repository](https://github.com/flutter/agent-plugins).
Follow its [setup guide](https://docs.flutter.dev/ai/get-started) for SDK and client
requirements. This provider is separate from the company-owned Product and
Engineering kits; its skills and Dart MCP server are not copied into this repo.
requirements. The official provider supplies the general skills and the Dart MCP
server. Bitwild Team Kit supplies the specialist Dart, Flutter, and package workflows.
[Team skill catalog](../plugins/bitwild-team-kit/README.md)

## Install

Expand All @@ -24,6 +25,18 @@ The plugin configures `dart mcp-server`. Avoid duplicate Dart skill providers or
MCP configurations. A new session should expose the selected skills and server;
installation alone does not establish successful application testing.

## Hosted environments

Install for the client that owns the project checkout. Each machine or cloud runner needs access to the SDK. In an ephemeral environment, put SDK provisioning in its image or setup script and verify discovery in a fresh session.

| Target | How to configure it |
| --- | --- |
| Codex CLI on a remote machine | Use the Codex commands above in the runner’s active profile. Check that an official skill is visible and that Dart MCP returns tools there. [Codex cloud environments](https://developers.openai.com/codex/cloud/environments/) |
| Claude.ai chat | In **Customize → Plugins → Add marketplace**, add `flutter/agent-plugins` and select Dart and Flutter. Chat loads skills. Its MCP connectors require a remote URL, while Flutter ships a local command. [Claude platform support](https://claude.com/docs/plugins/platform-support) |
| Claude Code on the web | Provision the SDK in the cloud environment. For a single-repository session, a project `.mcp.json` can register `dart mcp-server` when no plugin provides it. Check the account’s enabled skills in the cloud session. [What carries over](https://code.claude.com/docs/en/cloud-environments#what-carries-over-from-your-setup) |
| Grok Bot | Search **Connect apps** for Dart and Flutter. If unavailable, provision Dart on the Bot’s computer and add a **Command** connector with command `dart` and argument `mcp-server`. This configures MCP only. [Bot connectors](https://docs.x.ai/grok-bot/computer-and-apps#connect-an-app) |
| ChatGPT chat | On a workspace with custom apps enabled, connect a hosted HTTPS MCP endpoint through the app settings. Flutter supplies a command to run beside the checkout. A hosted connector needs its own runtime and access to the intended project. [Connect a custom MCP app](https://developers.openai.com/apps-sdk/deploy/connect-chatgpt/) |

## Update the external provider

Use the client's native plugin manager when an update is wanted:
Expand Down
10 changes: 10 additions & 0 deletions plugins/bitwild-team-kit/.claude-plugin/plugin.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,10 @@
{
"name": "bitwild-team-kit",
"version": "1.0.0",
"description": "Plan product delivery, design interfaces, write documentation, review engineering changes, and build with Dart and Flutter.",
"author": {
"name": "Bitwild"
},
"repository": "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/btwld/agent-plugins",
"skills": "./skills/"
}
26 changes: 26 additions & 0 deletions plugins/bitwild-team-kit/.codex-plugin/plugin.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,26 @@
{
"name": "bitwild-team-kit",
"version": "1.0.0",
"description": "Plan product delivery, design interfaces, write documentation, review engineering changes, and build with Dart and Flutter.",
"author": {
"name": "Bitwild"
},
"repository": "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/btwld/agent-plugins",
"skills": "./skills/",
"interface": {
"displayName": "Bitwild Team Kit",
"shortDescription": "Product, design, engineering, and Dart workflows",
"longDescription": "Plan product delivery, design interfaces, write documentation, review engineering changes, and build with Dart and Flutter.",
"developerName": "Bitwild",
"category": "Coding",
"capabilities": [
"Read",
"Write"
],
"defaultPrompt": [
"Review this change for merge readiness.",
"Turn these requirements into a delivery breakdown.",
"Help me use the Dart package version installed in this project."
]
}
}
File renamed without changes.
7 changes: 7 additions & 0 deletions plugins/bitwild-team-kit/LICENSE
Original file line number Diff line number Diff line change
@@ -0,0 +1,7 @@
Bitwild Team Kit includes components with different licensing terms.

The included BSD-3-Clause, MIT, and Apache-2.0 notices apply to the corresponding
components identified in SOURCES.md. Original license texts are provided in
licenses/ and in the skill directories where applicable. The product schema,
company generators, and document reference assets retain their existing terms.
Bundling them with other components does not grant a new license to those files.
Loading