-
Notifications
You must be signed in to change notification settings - Fork 54
Description
Feature Summary
When using the /RunbookLink command, provide the option to create an empty "placeholder" runbook within the same workspace.
Problem/Use Case
Would be very useful when laying out a new runbook from a "top-down" perspective. Would help instinctively guide end-users to a more modular workflow.
Proposed Solution
If the current typed text doesn't match any existing runbooks, provide the option to create a new runbook with that name when enter is pressed.
Current Workaround
None, just get slightly annoyed and create the given runbook.
Detailed Description
User Interface
Per above proposal
Integration Points
Would this feature need to integrate with:
- Shell/Terminal
- Database clients
- HTTP/API calls
- File system
- External tools (specify): ___
- Other: ___
Alternatives Considered
None
Additional Context
- Priority: Low
- Frequency: Daily
- Team Impact: Its a personal annoyance, but would be widely used
Related Issues/Discussions
I didn't find anything when searching, so this might be more of a me issue. But - it is an established workflow for applications like Obsidian.
Implementation Notes
I think a "quick and dirty" implementation that only creates a blank runbook in the parent workspace would be a great trial balloon. As I said above, I might be an edge case, but I do think this is a great quality of life feature for modularizing more complex workflows.