fstack

name	fstack
version	0.7.0
description	Full-stack engineer's companion. Router and setup entrypoint. Detects which archetype you're working in (production, sprint, exploration, etc.) from observed behavior and suggests a switch when context changes.
allowed-tools	["Bash","Read","Write","Edit","AskUserQuestion","Skill"]
triggers	["fstack","set up fstack","configure fstack","show my fstack profile","which archetype am I in","switch profile"]

/fstack

Entrypoint. Setup on first use. Otherwise: auto-detect mode, route, summarize.

Preamble

_FSTACK_BIN=""
_skill_md="$HOME/.claude/skills/fstack/SKILL.md"
if [ -L "$_skill_md" ]; then
  _src="$(readlink "$_skill_md")"
  _FSTACK_BIN="$(cd "$(dirname "$_src")/../bin" && pwd)"
fi
if [ ! -x "$_FSTACK_BIN/fstack-config" ]; then
  for cand in "$HOME/Workspaces/fstack/bin" "$HOME/fstack/bin" "$HOME/src/fstack/bin"; do
    [ -x "$cand/fstack-config" ] && _FSTACK_BIN="$cand" && break
  done
fi
echo "FSTACK_BIN: $_FSTACK_BIN"

if [ ! -x "$_FSTACK_BIN/fstack-config" ]; then
  echo "FSTACK_STATE: missing-bin"
elif "$_FSTACK_BIN/fstack-config" exists; then
  "$_FSTACK_BIN/fstack-config" migrate >/dev/null 2>&1 || true
  echo "FSTACK_STATE: ready"

  _last="$("$_FSTACK_BIN/fstack-config" get profile.last_cluster_at)"
  _obs="$("$_FSTACK_BIN/fstack-observe" path 2>/dev/null)"
  _n_obs=0; [ -f "$_obs" ] && _n_obs="$(wc -l < "$_obs" | tr -d ' ')"
  _do_cluster=no
  if [ "$_n_obs" -ge 5 ]; then
    if [ -z "$_last" ] || [ "$_last" = "null" ]; then
      _do_cluster=yes
    else
      _last_epoch=$(date -j -f "%Y-%m-%dT%H:%M:%SZ" "$_last" +%s 2>/dev/null || date -d "$_last" +%s 2>/dev/null || echo 0)
      _now_epoch=$(date +%s)
      _age_h=$(( (_now_epoch - _last_epoch) / 3600 ))
      [ "$_age_h" -gt 24 ] && _do_cluster=yes
    fi
  fi
  [ "$_do_cluster" = "yes" ] && "$_FSTACK_BIN/fstack-cluster" cluster >/dev/null 2>&1 || true

  _suggest_on="$("$_FSTACK_BIN/fstack-config" get profile.auto_suggest)"
  _pinned="$("$_FSTACK_BIN/fstack-config" get profile.pinned)"
  _active="$("$_FSTACK_BIN/fstack-config" active)"
  echo "ACTIVE: $_active"
  echo "AUTO_SUGGEST: $_suggest_on"
  [ -n "$_pinned" ] && [ "$_pinned" != "null" ] && echo "PINNED: $_pinned"
  if [ "$_suggest_on" = "true" ] && { [ -z "$_pinned" ] || [ "$_pinned" = "null" ]; }; then
    _match="$("$_FSTACK_BIN/fstack-cluster" match 2>/dev/null)"
    if [ -n "$_match" ] && [ "$_match" != "$_active" ]; then
      _repo="$(git rev-parse --show-toplevel 2>/dev/null | awk -F/ '{print $NF}')"
      _branch="$(git branch --show-current 2>/dev/null || echo "")"
      echo "SUGGEST: $_match (matches ${_repo:-?}:${_branch:-?}, current $_active)"
    fi
  fi

  echo "INSTALL_MODE: $("$_FSTACK_BIN/fstack-config" get install.mode)"
  echo "BUILDER PROFILES:"
  "$_FSTACK_BIN/fstack-profile" list | sed 's/^/  /'
  echo "ACTIVE_PRODUCT: $("$_FSTACK_BIN/fstack-config" active-product)"
  "$_FSTACK_BIN/fstack-product" summary | sed 's/^/  /'
  _declared="$("$_FSTACK_BIN/fstack-config" get-active declared_at)"
  [ -z "$_declared" ] && echo "DECLARED: no" || echo "DECLARED: yes"
  _prod_bound="$("$_FSTACK_BIN/fstack-config" get-product verify.command)"
  { [ -z "$_prod_bound" ] || [ "$_prod_bound" = "null" ]; } && echo "PRODUCT_BOUND: no" || echo "PRODUCT_BOUND: yes"
  echo "OBSERVATIONS_TOTAL: $_n_obs"
else
  echo "FSTACK_STATE: uninitialized"
fi

Branch

1. missing-bin. Tell the user fstack isn't on disk. Point at the installer. STOP.
2. uninitialized. Run ./install --dev from the repo root, then retry. STOP.
3. DECLARED: no and only one subprofile (default). Run Setup.
4. SUGGEST: line printed. Ask the user via AskUserQuestion: "Switch to <match>? Yes / No / Pin current." On Yes: "$_FSTACK_BIN/fstack-profile" use <match>. On Pin: "$_FSTACK_BIN/fstack-profile" pin. Then route or summarize.
5. PRODUCT_BOUND: no and the user is inside a git repo. Offer once: "This product isn't set up yet. Recon this repo and draft its profile?" Yes → /fstack-product (bootstrap). Don't nag on later runs.
6. Otherwise. Route or Summarize.

Setup

Setup writes into the active subprofile (always default on first run).

Offer first: "Walk seven dimensions now (≈1 minute), or skip with sane defaults and let me learn from your work?" If skip, set declared_at to now and stop. Observations and clustering take over.

If walking: seven AskUserQuestion calls, one at a time. Each dimension has two legitimate ends. Map A=0.2, B=0.5, C=0.8. Don't suggest one end is "better" than the other.

1. risk_tolerance. Stability / Balanced / Speed.
2. bias_for_action. Deliberate / Balanced / Action.
3. scope_appetite. Focused / Balanced / Ambitious.
4. test_rigor. Lean / Balanced / Rigorous.
5. architecture_care. Pragmatic / Balanced / Principled.
6. detail_preference. Detail-oriented / Balanced / Big-picture.
7. autonomy. Seek-permission / Balanced / Ask-forgiveness.

After each:

"$_FSTACK_BIN/fstack-config" set-active developer.<dim> <value>

After all seven:

"$_FSTACK_BIN/fstack-config" set-active declared_at "$(date -u +%Y-%m-%dT%H:%M:%SZ)"
"$_FSTACK_BIN/fstack-profile" vibe

Then: "Set up the product you're working on? I'll recon this repo and draft its profile (verify, gates, board, stack)." Yes → invoke /fstack-product (bootstrap).

Mention two things:

• "There are two profiles. The builder profile is how you work (I derive archetypes like production/sprint/exploration from your behavior and suggest a switch on context change; disable with fstack-config set profile.auto_suggest false). The product profile is what you build and how it ships. Both feed the way of working (WAY-OF-WORKING.md)."

Route

Match intent. Invoke via Skill tool.

User wants	Route
see profile / nothing typed	inline summary below
edit dimension or preference (how I work)	/fstack-profile
list / switch / pin builder profile	/fstack-profile
set up / switch / onboard a product	/fstack-product
edit verify / gates / board / owner-gated	/fstack-product
show the way of working / operating model	print WAY-OF-WORKING.md from the fstack repo
set stack / use X	/fstack-stack
add a skill	/fstack-skill
scaffold / new feature	/fstack-scaffold
design an api / endpoint	/fstack-api
new table / migration	/fstack-schema
ambiguous	ask: builder profile, product profile, stack, custom skill, scaffold, api, or schema?

Inline summary

"$_FSTACK_BIN/fstack-profile" vibe
"$_FSTACK_BIN/fstack-product" summary
"$_FSTACK_BIN/fstack-profile" stack

Then one line of next step:

• Only default and few observations. "Just go build. I'll learn your modes as you go."
• Multiple inferred subprofiles + suggestion present. "Looks like <key> mode here. Switch or stay?"
• 20+ observations and no inferred subprofiles emerged. "Your sessions look uniform so far. No distinct modes yet."
• Inferred subprofile active, ≥ 0.2 gap on any dim. "Your behavior in this mode is drifting from declared. /fstack-profile gap."
• Otherwise. "Use /fstack-scaffold, /fstack-api, or /fstack-schema."

Observation logging

This skill doesn't log dimension signals. It can drop an annotation if the user states a behavioral preference in chat:

"$_FSTACK_BIN/fstack-observe" annotate "User wants full coverage on all backend changes" --skill fstack

Domain skills do the dimension logging.

Voice

Short. Direct. Suggest, don't switch. When the user accepts a switch, confirm in one line ("active: production"). When they decline, drop it. Don't re-prompt the same suggestion.