docs: add nanopm to community schemas catalog#1109
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✅ Files skipped from review due to trivial changes (1)
📝 WalkthroughWalkthroughOne new row was added to the Community Schemas table in the customization documentation, registering ChangesCommunity Schemas Documentation
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 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 |
- README: add "Works with OpenSpec" section with two-layer table and handoff example - pm-scan: detect openspec/specs/, read specs before synthesis, surface spec/test gaps in SCAN.md - pm-breakdown: detect OpenSpec, add change folder as write target (proposal + design + tasks + specs/) - openspec-schema/: proper community schema (schema.yaml + 4 templates) for OpenSpec catalog PR to OpenSpec catalog: Fission-AI/OpenSpec#1109 Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@docs/customization.md`:
- Line 349: The docs entry for the nanopm schema omits the design artifact
mapping; update the nanopm row (identify by `nanopm`, `@nmrtn`, and
`nmrtn/nanopm`) to explicitly state that the schema maps `design <- strategy` in
addition to proposal/tasks sourcing from `.nanopm/`, e.g. mention that the
`design` artifact is sourced from the `strategy` output so readers see the full
bridge behavior between planning and OpenSpec artifacts.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: 1655c7ac-f2ce-4e5e-9daf-cd5d0e654dfe
📒 Files selected for processing (1)
docs/customization.md
What this adds
Adds nanopm to the community schemas table in
docs/customization.md.nanopm is a PM automation skill pack for Claude Code. It runs the full planning cycle (audit → strategy → roadmap → PRD) and the
openspec-schema/in its repo is a proper OpenSpec schema that bridges the PM layer to OpenSpec's engineering workflow.The schema
The schema lives at
nmrtn/nanopm/openspec-schema/and follows the standard structure:When generating artifacts, it reads from
.nanopm/if present — so the proposal sources the audit findings, tasks source the PRD breakdown, and design sources the strategy. No copy-paste between tools.Install (for users)
Summary by CodeRabbit