docs: add working-with-aidlc interaction guide and writing-inputs documents

[harmjeff]

Summary

• Adds working-with-aidlc.md — a practical guide covering interaction patterns, tips, and examples drawn from real workshop experience, covering the full workflow from Inception through Construction
• Adds writing-inputs/ folder with guides and templates for preparing Vision and Technical Environment documents before starting a project
• Updates README.md Additional Resources table with a reference to working-with-aidlc.md

Test plan

• Verify all links in README.md pointing to working-with-aidlc.md resolve correctly
• Verify all internal links within working-with-aidlc.md (e.g. to writing-inputs/ files) resolve correctly
• Review writing-inputs/inputs-quickstart.md for greenfield and brownfield quick-start paths
• Review writing-inputs/vision-document-guide.md and writing-inputs/technical-environment-guide.md for completeness

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the project license.

[scottschreckengaust]

Consider placing files under docs

[harmjeff]

All @scottschreckengaust requests are completed

[spraja08]

Reviewed. Good to go.

[scottschreckengaust]

LGTM

[Kalindi-Dev]

@harmjeff
This is nitpicky and can be added to subsequent releases:

1. WORKING-WITH-AIDLC.md:118 — "If your tool offers a 'compact context' prompt mid-workflow, always decline it" is strong advice that may become outdated as context management in AI tools evolves. Consider softening to something like "compaction mid-workflow is generally less reliable than a clean
   reset."

2. WORKING-WITH-AIDLC.md:555 — "This flow takes a few extra minutes compared to directly editing a file." Contains an implicit time estimate. Minor, but could be rephrased as "This flow takes extra steps compared to directly editing a file."

Looks good to me otherwise.