Conversation
* feat: distribute CIS as plain skills through npx skills CIS becomes a module that installs and updates through `npx skills`, with no installer. This includes the work from #43, rebased onto main, plus the module help, roster, and dependency declarations that followed it. Layout - Move the ten skills from src/skills/ to a repo-root skills/ tree, which is the only place `npx skills` installs from. - Delete src/module.yaml, src/module-help.csv and the plugin marketplace manifest. Nothing reads them on the new path. - Prune eslint ignores and sixteen devDependencies inherited from BMAD-METHOD that had no counterpart or importer here. Manifests - Every skill carries module-manifest.toml: module, version, update_source, knowledge, roster, requires and recommends. - Every skill requires the bmad hub skill 6.13.0 or later. - Every skill recommends bmad-advanced-elicitation, bmad-customize, bmad-forge-idea and bmad-party-mode. Personas also recommend the skill behind their menu. Help and roster live in the skills - knowledge was a link to the docs site llms.txt, so help had nothing local to read. It is now a list of documents each skill carries: bmad-meta/cis-help.md in all ten skills, bmad-meta/agents-help.md in the six personas. The content replaces what module-help.csv held. - bmad-meta/cis-roster.toml, named by the new roster key, holds what module.yaml's agents list held: the six personas as party members, four guest members, and two groups (creative-studio, midnight-salon). It uses the fields bmad-party-mode already uses. Party mode does not read it yet. - These files are edited once in bmad-meta/ at the repo root. tools/sync_knowledge.py copies each into the skills whose manifests name it, under any key, and removes a shared copy a manifest stops naming. npm test fails when the copies drift or a roster group names a member nobody defines. Skills - Resolve central config through _bmad/scripts/resolve_config.py instead of the module-era _bmad/cis/config.yaml. - When the resolver script is missing, offer the bmad skill's setup, installing bmad first when the agent has no such skill. Personas offer to install a menu skill that is not present. - Drop user name and language config from skill prose. Release tooling - tools/stamp_release.py writes a version into every manifest and tools/release.md is the runbook. The stamper validates knowledge and roster files, requires and recommends entries, and accepts manifest keys it does not know, since the runtime ignores them. Only the top-level version line is rewritten, and the stamp fails if anything else changed. Still open: update_source points at the cis-skills mirror repository. Co-authored-by: Alex Verkhovsky <alexey.verkhovsky@gmail.com> * chore(release): release from this repository with a dev branch The cis-skills mirror is being removed. update_source now names this repository in every manifest and in the stamper. tools/release.md follows the BMAD-METHOD procedure: dev receives PRs, main is release-only and is what npx skills installs, and a release fast-forwards main to a stamped commit on dev and tags it. * chore: remove the npm release workflow and version field Releases are now a stamped commit promoted from dev to main, so the workflow that ran npm version and pushed to main can no longer be used, and would break main staying an ancestor of dev. package.json loses its release scripts, publishConfig, empty main and bin, and its version: the manifests are the only version source. * chore: set the placeholder to 0.4.0-next and check bmad-meta copies in CI - README installs CIS with npx skills and names the real skills; the old installer command and /cis-* commands no longer exist. - quality.yaml runs tools/sync_knowledge.py, which until now only ran in the local hook, so a PR with stale bmad-meta copies can no longer merge. - 0.3.2 is already released, so the placeholder becomes 0.4.0-next and personas recommend their menu skill at 0.4.0. --------- Co-authored-by: Alex Verkhovsky <alexey.verkhovsky@gmail.com>
* feat!: replace per-skill module metadata with a bmod module record
The module is now one folder, skills/bmod-cis, holding bmod.toml, a stub SKILL.md, help/help.md with three topic files, and roster.toml. Each member skill carries a bmod.toml with a [skill] table. The root bmad-meta folder, its 26 per-skill copies, the ten module-manifest.toml files and tools/sync_knowledge.py are removed.
- help.md leads with the six agents, then the four sessions with what each works through and writes. It no longer points at the documentation site, which is out of date.
- bmad-brainstorming is recommended by the module and is on the menus of Maya, Dr. Quinn and Victor as well as Carson, who no longer requires it.
- Caravaggio's menu drops the Excalidraw wording and goes from seven prompts to four: plan (PL), critique (CR), video explainer (EX), visual (VM).
- Storytelling offers all 25 frameworks in its library instead of a fixed ten, and reads the key_questions column the file actually has.
- Session documents are named <stem>-{topic_slug}-{date}.md and a session never overwrites an earlier one.
- Sessions read a document the user names instead of a "data attribute".
- Agents hand off to the bmad skill instead of bmad-help.
- tools/stamp_release.py stamps the [bmod] version and has a --check mode that npm test runs. CI also runs BMAD-METHOD's validate_manifests.py against this repository.
BREAKING CHANGE: module-manifest.toml and bmad-meta are gone; installs need bmod-cis and bmad 6.13.0. Caravaggio's menu codes SD, PD, CT, IN and CV are removed. Session output file names now include the topic.
* fix: check a stamp before writing, require a source on table dependencies, and handle a missing pause skill
- stamp_release.py compares each stamped file with what it should be before anything is written, so a bad stamp never reaches disk.
- A table-form required or recommended skill must give a source, as the runtime requires. Only a plain name of a skill in this repository goes without one.
- The four sessions say so and offer the install command when the user picks advanced elicitation or party mode and that skill is not installed.
- The help no longer says a persona's name and title can be customized.
|
Note Currently processing new changes in this PR. This may take a few minutes, please wait... ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: ⛔ Files ignored due to path filters (6)
📒 Files selected for processing (51)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.