Query: Monorepo setup, subsquads migration, and persistence issues (v0.9.1) #943

Monorepo setup, subsquads migration, and persistence issues (v0.9.1)

Hi, I’m trying to use Squad in a monorepo setup and ran into a few issues. Would appreciate some guidance.

Context

• Repo structure:

  C:\Users\reporoot
  ├── apps
  │   ├── project1
  │   └── project2
  └── lib
      ├── internal
      │   └── xmlparser
      └── thirdparty
          └── openssl
  

• project1 and project2 both depend on openssl

• project2 also depends on xmlparser

• I primarily work on project1

Issues / Questions

1. Squad initialized in subfolder

   • I ran squad init inside apps\project1
   • It created a .git inside project1, which I don’t want (monorepo already has its own root git)
   • For now, I’ve been manually deleting .git

   👉 What is the correct way to move this setup so Squad lives at reporoot level?

2. Migrating to subsquads

   • I believe I should use subsquads for project1 and project2
   • What’s the proper way to migrate from my current setup (initialized inside project1) to a root-level squad with subsquads?
   • Are there recommended steps to avoid breaking existing configuration?

3. Handling shared dependencies

   • Both projects use lib\thirdparty\openssl
   • project2 also uses lib\internal\xmlparser

   👉 How should Squad model shared folders like this?

   • Should openssl be its own squad?
   • Or referenced differently?

4. Missing skills file (v0.9.1)

   • I’m using:

     squad --version
     0.9.1
     

   • I don’t see any skills file being created

   👉 Is this expected in this version, or am I missing something?

5. Lack of persistence across sessions

   • I’ve repeatedly told Squad that builds must be run from:

     C:\Users\reporoot
     build.bat
     

   • It remembers during a session, but forgets in a new Copilot session

   • decision.md does not capture this
     Directives like "Always remember", "Never forget" etc don't help.

   👉 How do I make this kind of instruction persist reliably?

6. Defining repeatable workflows (build + test execution)

   • I want Squad to consistently follow this workflow:

     1. Make code changes
     2. Run build.bat (from repo root)
     3. Run test.bat to build tests
     4. Navigate to test output directory
     5. Execute project1.exe to verify all tests pass

   👉 What is the recommended way to define and persist such workflows?

   • Should this go into decisions, skills, or another mechanism?
   • How can I ensure this runs automatically or is consistently followed?

Thanks in advance—really like the idea behind Squad, just trying to get it working cleanly in a monorepo setup.