a ticket_id variable that auto-namespaces output

[darrylwolfaardt]

Describe your idea
I want to maintain a full specification history. Currently each new branch will overwrite other branches content with the default Agile/BMAD artefacts. I would like to run a BMAD process that is context sensitive to my branch.

Something like this
Structure output by ticket:
_bmad-output/
├── RZP-593/
│ ├── prd.md
│ ├── architecture.md
│ └── epics.md
└── RZP-594/
├── prd.md
└── ...

Why is this needed?
This is closely aligned to spec driven development and ensure we can come back and review the specification and decisions made even if the branch was deleted after PR.

How should it work?
When starting the process you could invoke a branch or feature reference, example:

• planning_artifacts: "{project-root}/_bmad-output/RZP-593"
• implementation_artifacts: "{project-root}/_bmad-output/RZP-593/stories"

[coderabbitai]

🔗 Related PRs

#2105 - refactor(quick-dev): replace unconditional artifact scan with intent cascade [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[darrylwolfaardt]

Naturally if I have missed this as an existing feature please point me in the right direction ;)