5 ms·

Can you please add more details? Thank you in advance!

• pixelsort 1mo ago
  I've been using my own variant docset driven development since late last year. It emerged organically for me by adapting to the limits of the agents. - Prefix-numbered sets of documents, keeping them clustered visually and easily referenced by humans and agents. (124.5 = docset 125, phase 5) - Each doc gets a suffix. Most of the time STRATEGY is the first doc. Sometimes NOTES, DISCUSSION, or HANDOFF though. - Once the strategy doc is comprehensive, the multi-phase checklist PLAN doc can emerge. - During execution, the agent drives the PLAN while purposefully expanding lightly scaffolded phases before entry. - As the user, I drive a PROGRESS doc during the PLAN execution. This tracks the progression of my own questions and the important work summaries that I need for tracking the current work trajectory and for historic analysis over past decision-making. - Any concern that exceed the scope of the active docset numbers calls for a new one. - A "docs/archive" folder is kept where I sweep docsets into numbered eras. I have aliases and templates too, but DDD is so simple that it's overkill. Any modern reasoning agent can take the plain explanation above and understand you effortlessly when you say "open a new docset strategy" or "read docset 125 and proceed".
• 3371 1mo ago
  It's just good old prompting in skill format. You can check out the skill repo: no3371/projex