Agent skill · Documentation

spec-driven-collaboration

Generate self-contained collaboration documents for sharing issues with external AI systems (Gemini, ChatGPT, etc.) with structural anti-skip enforcement (Execute-Verify-Record pattern at every step). Interactively gathers context, reads actual code files, loads constitutional constraints, and produces a complete 10-section package ready to paste into the target LLM. Use when the user wants to collaborate with another AI, share an issue for joint problem-solving, get a fresh perspective from a peer LLM, or needs help from an external AI that doesn't have access to the codebase. Make sure to us

majiayu000github.com/majiayu000GitHub ↗
claude-codecopilotcan modify filesMIT
Install
npx skills add majiayu000/claude-skill-registry --skill spec-driven-collaboration-bankielewicz-devforgeai --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 7 KB
Bundled scripts: none
Allowed tools: -Read-Write-Glob-Grep-AskUserQuestion
Path: skills/ai-llm/spec-driven-collaboration-bankielewicz-devforgeai/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Spec-Driven Collaboration Generate a self-contained collaboration document that packages an issue with actual code, constitutional constraints, analysis, and targeted questions for an external AI to review. **Constitution files are THE LAW:** tech-stack.md, source-tree.md, dependencies.md, coding-standards.md, architecture-constraints.md, anti-patterns.md **If ambiguous or conflicts detected: HALT and use AskUserQuestion** --- ## Execution Model This skill expands inline. After invocation, execute Phase 01 immediately. Do not wait passively, ask permission, or offer execution options. **Self-Check (if ANY box is true = VIOLATION):** - [ ] Stopping to ask about token budget - [ ] Stopping to offer execution options - [ ] Waiting passively after skill invocation - [ ] Asking "should I execute this?" - [ ] Skipping a phase because it "seems simple" - [ ] Combining multiple phases into one - [ ] Summarizing instead of loading a reference file - [ ] Skipping verification because "I already wrote the file" **IF any box checked:** EXECUTION MODEL VIOLATION. Go directly to Phase 01 now. --- ## Anti-Skip Enforcement Contract This skill enforces structural anti-skip at every step using the

What's inside
Steps it walks through
  1. Execution Model
  2. Anti-Skip Enforcement Contract
  3. Parameter Extraction
  4. Phase Table
  5. Phase Orchestration Loop
  6. Success Criteria
  7. Reference Files
  8. Error Handling
Ships with 1 file
  • metadata.json
More from claude-skill-registry
All skills →
About this skill
What does the spec-driven-collaboration skill do?

Generate self-contained collaboration documents for sharing issues with external AI systems (Gemini, ChatGPT, etc.) with structural anti-skip enforcement (Execute-Verify-Record pattern at every step). Interactively gathers context, reads actual code files, loads constitutional constraints, and produces a complete 10-section package ready to paste into the target LLM. Use when the user wants to collaborate with another AI, share an issue for joint problem-solving, get a fresh perspective from a peer LLM, or needs help from an external AI that doesn't have access to the codebase. Make sure to us

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill spec-driven-collaboration-bankielewicz-devforgeai --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going