grow

Context

DEVLOOP_DIR="$HOME/.devloop"
PROFILE="$DEVLOOP_DIR/profile.md"
mkdir -p "$DEVLOOP_DIR/observations"
[ -f "$PROFILE" ] && echo "PROFILE_EXISTS=true" || echo "PROFILE_EXISTS=false"
echo "DEVLOOP_DIR=$DEVLOOP_DIR"
if [ -f "$HOME/.devloop/scripts/check-grow-ready.sh" ]; then
  bash "$HOME/.devloop/scripts/check-grow-ready.sh" --context 2>/dev/null
else
  echo "GROW_AVAILABLE=true"
fi

Routing

If PROFILE_EXISTS=false, read onboarding.md and follow its instructions.

If PROFILE_EXISTS=true:

• No arguments or empty $ARGUMENTS:
  • If GROW_AVAILABLE=false: respond with the value of COOLDOWN_MSG as plain text and stop. Do not read any other files.
  • Otherwise → read run.md and follow its instructions
• $ARGUMENTS = "me" → read me.md and follow its instructions
• $ARGUMENTS = "history" → read history.md and follow its instructions

---

Find Content

ONLY use content from sources listed in sources.md. Run this entire section silently.

Step 1: Target

Read profile.md, observations, and history.jsonl. Identify 3-5 growth opportunities, ranked with reasoning. Don't search yet. For each:

• Which concept(s) it addresses
• Impact: A 0-1 concept or recurring cross-domain pattern from Deep Patterns? Does fixing this unlock progress in other domains? A tool that eliminates their current approach? Generally: product direction > tools/workflow > approach > skill gaps, but not rigid. Mindset-level feedback is the most personal and requires established trust.
• Readiness: Is the user bumping into this right now, or is it important in the abstract? A user mid-build may need building advice. A user who just shipped may need distribution advice.
• Pacing: Repeat topics from history.jsonl only if strategic. Think twice before pushing topics where past recommendations were ignored.

Step 2: Explore

Two parallel Sonnet subagents. They explore wide and return a menu of candidates, not a committed topic: