spec-driven-collaborationlisted
Install: claude install-skill bankielewicz/DevForgeAI
# 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/, dependencies.md, coding-standards.md, architecture-constraints.md, anti-patterns.md
**If ambiguous or conflicts detected: HALT and use AskUserQuestion**
---
## Execution Model
See **`.claude/rules/core/anti-skip-behavior.md`** for the canonical execution contract (expand inline; do not wait passively or offer execution options; honor every step of every phase; Self-Check violation taxonomy; Token-Optimization-Bias prohibition; governed by ADR-076). After invocation, execute Phase 01 immediately.
---
## Anti-Skip Enforcement Contract
Enforced structurally outside LLM control, not by this prose — by the framework's deterministic gates wired for this workflow: the `devforgeai-validate` phase gates, the `settings.json`-registered `.claude/hooks/` scripts, and `.claude/hooks/phase-steps-registry.json` (ADR-076). Behavioral residue: `.claude/rules/core/anti-skip-behavior.md`.
---
## Parameter Extraction
Extract parameters from conversation context set by the `/collaborate` command:
| Context Marker | Set By | Description |
|----------------|--------|-------------|
| `ISSUE_DESCRIPTION` | /collaborate | Issue description from user argument or AskUserQuestion |
| `TARGET_AI` | /collaborate | Target AI