Thank you for your interest in contributing. IDD is an early, evolving framework and we welcome input from practitioners who are experimenting with AI-assisted development processes.
The most valuable contribution right now is real-world feedback. If you've tried IDD (or parts of it), open a Discussion and share:
- What worked well?
- What didn't fit your team or context?
- What artifacts or concepts needed adjustment?
- What's missing from the framework?
If you find errors, unclear language, or gaps in the documentation, open an Issue. Please include:
- Which document the issue is in
- What you expected vs. what you found
- A suggestion for improvement (if you have one)
For documentation improvements, new examples, or framework refinements:
- Fork the repository
- Create a branch (
feature/your-change) - Make your changes
- Submit a Pull Request with a clear description of what changed and why
We especially welcome worked examples from different domains and team sizes. If you've applied IDD to a project, consider contributing an example following the format in examples/. Remove any proprietary or identifying information.
- Keep it practical. IDD is a practitioner's framework. Contributions should be grounded in real experience, not theoretical speculation.
- Be opinionated but open. IDD takes specific positions (flow over sprints, specs over stories). Contributions should engage with these positions, not dilute them. But reasoned disagreement is welcome.
- Use clear language. Avoid jargon where simpler words work. The audience includes product owners and developers, not just process consultants.
- Maintain the structure. New artifacts, roles, or metrics should follow the existing patterns and formatting.
Be respectful, constructive, and professional. We're all figuring this out together.
By contributing, you agree that your contributions will be licensed under CC BY-SA 4.0.