Handling of independent tasks (not tied to a feature)

[cmelan]

Hello,
I have a suggestion regarding stand alone tickets -- if there is any other way to handle it would be happy to hear as well.

Description:
Currently, when creating an independent task (e.g., bug fixes, standalone improvements), there is no clear instruction on where the tasks.md file should be placed.

As a result:

• Sometimes the file is created in the root folder.
• Other times, it incorrectly attempts to generate a spec folder and place it there.

Proposed Solution:
Independent tasks should be explicitly defined and kept independent from feature specs. For example:

• Place them in a dedicated independent/ folder (e.g., .agent-os/independent/[task-name]/tasks.md),
• Or another clearly documented location outside of feature-bound specs.

This ensures that bugs, standalone improvements, and non-feature tasks remain properly tracked without being mixed into feature folders.

[jellydn]

At times, we will have an adhoc task or mics tasks for improvement. What is the flow with agent-os?

[mikelittle]

Here is my quick and dirty solution, #147 (comment)