starred/planning-with-files

Fork 0

mirror of https://github.com/OthmanAdi/planning-with-files.git synced 2026-04-25 16:06:02 +03:00

[GH-ISSUE #28] devis based on planning-with-files #19

New issue

Closed

opened 2026-03-03 18:50:01 +03:00 by kerem · 1 comment

kerem commented

2026-03-03 18:50:01 +03:00

Owner

Originally created by @st01cs on GitHub (Jan 14, 2026).
Original GitHub issue: https://github.com/OthmanAdi/planning-with-files/issues/28

A new project named devis was created based on planning-with-files.

https://github.com/st01cs/devis

Key features:

Automatically generate new plans through interviews.
Use Claude's command mechanism to trigger, preventing Claude's skill mechanism from being missed.

Thank you for creating such a great planning-with-files.

Originally created by @st01cs on GitHub (Jan 14, 2026). Original GitHub issue: https://github.com/OthmanAdi/planning-with-files/issues/28 A new project named devis was created based on planning-with-files. https://github.com/st01cs/devis Key features: - Automatically generate new plans through interviews. - Use Claude's command mechanism to trigger, preventing Claude's skill mechanism from being missed. Thank you for creating such a great planning-with-files.

kerem closed this issue

2026-03-03 18:50:02 +03:00

kerem commented

2026-03-03 18:50:03 +03:00

Author

Owner

@OthmanAdi commented on GitHub (Jan 17, 2026):

Hi @st01cs,

This is AMAZING! I just checked out devis and I'm genuinely impressed with what you've built!

What I Love About Devis 🎉

The Interview Phase - This is brilliant! Starting with /devis:intv to clarify requirements through structured questioning before jumping into implementation is exactly the kind of workflow improvement planning-with-files needed. You've solved a real problem here.

Command Mechanism - Using /devis:intv and /devis:impl commands instead of relying on skill auto-activation is smart. This actually addresses one of the issues users reported (#31) where the skill doesn't always trigger. Your approach guarantees activation every time.

Same Philosophy, Better Execution - You kept the core 3-file pattern (task_plan.md, findings.md, progress.md) and filesystem-as-memory approach, but made it more structured and reliable. That's exactly how open source should work!

This is How Community Should Work

You:

Built something genuinely useful
Extended the concept in a meaningful way
Gave a kind shoutout in your issue
Made something BETTER

That's the dream of open source right there.

What Happens Next

I'm adding devis to the Community Forks section in README.md with a proper spotlight on what makes it unique. Your interview-first approach and command mechanism are innovations worth highlighting.

Just a simple mention of planning-with-files in your README (which you already have!) is perfect. That's all the "attribution" that matters - users understanding where ideas came from.

Can We Collaborate?

I'd love to learn from what you've built:

The interview structure looks really valuable
The command mechanism solves real activation issues
Session resumption is clever

Would you be open to:

Maybe doing a writeup on the interview phase approach?
Sharing any lessons learned that could help planning-with-files users?
Listing devis in the Community Forks with your description?

No pressure at all - you've already contributed by building something great and showing what's possible with this pattern.

Thank you for building devis and for the kind words about planning-with-files. Seeing people take an idea and make it better is the best feeling in open source.

Keep building awesome things!

Ahmad

@OthmanAdi commented on GitHub (Jan 17, 2026): Hi @st01cs, This is AMAZING! I just checked out devis and I'm genuinely impressed with what you've built! ## What I Love About Devis 🎉 **The Interview Phase** - This is brilliant! Starting with `/devis:intv` to clarify requirements through structured questioning before jumping into implementation is exactly the kind of workflow improvement planning-with-files needed. You've solved a real problem here. **Command Mechanism** - Using `/devis:intv` and `/devis:impl` commands instead of relying on skill auto-activation is smart. This actually addresses one of the issues users reported (#31) where the skill doesn't always trigger. Your approach guarantees activation every time. **Same Philosophy, Better Execution** - You kept the core 3-file pattern (task_plan.md, findings.md, progress.md) and filesystem-as-memory approach, but made it more structured and reliable. That's exactly how open source should work! ## This is How Community Should Work You: - Built something genuinely useful - Extended the concept in a meaningful way - Gave a kind shoutout in your issue - Made something BETTER That's the dream of open source right there. ## What Happens Next I'm adding devis to the Community Forks section in README.md with a proper spotlight on what makes it unique. Your interview-first approach and command mechanism are innovations worth highlighting. Just a simple mention of planning-with-files in your README (which you already have!) is perfect. That's all the "attribution" that matters - users understanding where ideas came from. ## Can We Collaborate? I'd love to learn from what you've built: - The interview structure looks really valuable - The command mechanism solves real activation issues - Session resumption is clever Would you be open to: 1. Maybe doing a writeup on the interview phase approach? 2. Sharing any lessons learned that could help planning-with-files users? 3. Listing devis in the Community Forks with your description? No pressure at all - you've already contributed by building something great and showing what's possible with this pattern. --- **Thank you** for building devis and for the kind words about planning-with-files. Seeing people take an idea and make it better is the best feeling in open source. Keep building awesome things! Ahmad

No labels

bug

pull-request

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/planning-with-files#19

No description provided.

Rows
Columns