Welcome to planning-with-files Discussions!

[OthmanAdi]

👋 Welcome!

We’re using Discussions as a place to connect with other members of our community. We hope that you:

• Ask questions you’re wondering about.
• Share ideas.
• Engage with other community members.
• Welcome others and are open-minded. Remember that this is a community we
  build together 💪.

To get started, comment below with an introduction of yourself and tell us about what you do with this community.

[OthmanAdi]

Hello everyone. a big thank you from me for the forks and stars. you gave me one of the happeist days of my life as an OSS developer. thank you for making my sleepless night i chose for the project worthit. it was all for you.

[OthmanAdi]

Im open for assigning a successor btw.

[REY-HIDDEN]

how we can communicte each other to share project and tasks gave me the link

[OthmanAdi]

@REY-HIDDEN my deepest apologies for not seeing this man! please add me on https://www.linkedin.com/in/codingwithadi/ or https://x.com/OthmanAmmarAdi drop me your link

[FaithChen909]

Could you share some ways/tips to use planning-with-files with hookify or hooks in Claude code?

[OthmanAdi]

Good question. You don't need hookify or any extra setup, the hooks are already built into the skill and activate automatically.

But let me explain what they actually do for you in practice:

When you start a task and create your planning files, the hooks work in the background to keep you on track:

Before you write code — the skill automatically re-reads your task_plan.md. This means even after 50+ tool calls when Claude starts drifting, it gets pulled back to your actual goal. You don't have to keep reminding it "remember the plan."

After you edit files — you get a gentle nudge to update your progress. Easy to forget when you're deep in implementation. The hook catches that.

Before Claude stops — it checks if all your phases are actually done. Prevents the "wait I wasn't finished" moment.

When you start a new session — if you had to /clear because context filled up, the skill tries to recover what happened in your last session so you're not starting blind.

Tips that actually help:

Break your task into clear phases in task_plan.md. The more specific, the better the hooks work.

After finishing a phase, tell Claude "mark phase X complete" explicitly. The PostToolUse hook will remind you but being explicit helps.

Use findings.md aggressively. Anything you discover that might matter later, dump it there. The hooks keep task_plan.md in attention but findings.md is your external brain.

If Claude seems confused mid-session, just say "re-read task_plan.md" and it'll re-orient.

The whole point is you shouldn't have to think about the hooks. They're there to make the workflow feel natural. If you're fighting them, something's off.

Let me know if you run into specific issues, happy to help troubleshoot.

Ahmad

[DonHuskini]

Any suggestions on how to handle backlog tasks, order them and also completed ones? The structure I created was a backlog folder that already has the expected file structure. Then this task is promoted to active, and active is moved to an archive folder. Do you agree with this pattern or do you have a different suggestion? Thanks for the skill, really nice.