fact-toolkit 0.1.0__py3-none-any.whl

fact/__init__.py

@@ -0,0 +1,3 @@
+"""FACT — Focused Agentic Context Toolkit."""
+
+__version__ = "0.1.0"

fact/_data/commands/fact-audit.md

@@ -0,0 +1,24 @@
+---
+description: Run a security / architecture / quality audit on demand.
+---
+
+Load the `fact-audit` skill and run an audit.
+
+The user may pass a dimension as argument:
+- `/fact-audit security`
+- `/fact-audit architecture`
+- `/fact-audit quality`
+- `/fact-audit` or `/fact-audit all` → run all three in parallel
+
+Use sub-agents per fact-audit §3 (Sonnet for deep reviews, Haiku for
+narrow per-task checks). Confirm any skill installation with the user
+before downloading.
+
+Write each audit report to `.specify/fact/audits/<UTC>-<dimension>.md`
+with the YAML frontmatter described in fact-audit §4 so the dashboard
+can render the severity badges.
+
+After the run:
+- If any critical finding → halt and present.
+- Otherwise summarize counts in chat and tell the user where each
+  full report lives.

fact/_data/commands/fact-next.md

@@ -0,0 +1,23 @@
+---
+description: Continue the current FACT phase or advance to the next.
+---
+
+Load `fact-rpi-harness` if you haven't already in this session.
+
+Identify the current phase from the state of files under `.specify/`:
+
+- No `constitution.md` → phase **constitution** (`/speckit.constitution`).
+- Constitution but no `spec.md` → phase **specify** (load `fact-discovery` or
+  `fact-research` depending on workflow type).
+- Spec but no `plan.md` → phase **plan** (`/speckit.plan`).
+- Plan but no `tasks.md` → phase **tasks** (`/speckit.tasks`).
+- `tasks.md` with pending tasks → phase **implement** (load `fact-implement`).
+- All tasks done → ask whether to start another feature, refactor, or wrap up.
+
+Before starting:
+1. Read `.specify/fact/session_state.json` to know which task was active.
+2. Read the latest file in `.specify/fact/sessions/` (semantic summary).
+3. If the active task was abandoned mid-flight, apply fact-onboarding §3b
+   ("abandoned task" case).
+
+Be brief. The user wants to make progress, not read a status report.

fact/_data/commands/fact-start.md

@@ -0,0 +1,19 @@
+---
+description: Start (or resume) a FACT workflow.
+---
+
+Load the `fact-rpi-harness` skill first (40% rule, sub-agents, intentional
+compaction, session-summary format) — keep it active for the whole session.
+
+Then load the `fact-onboarding` skill and follow its protocol:
+
+1. If `.specify/fact/session_state.json` or files under
+   `.specify/fact/sessions/` exist, this is a **resumed session** — apply the
+   "resume protocol" (§3 of fact-onboarding). Do NOT greet with "hi, I'm
+   FACT"; jump straight into presenting continuity.
+
+2. If no prior state exists, this is a **fresh project** — ask greenfield /
+   brownfield / demo and delegate to the matching skill.
+
+If a workflow is already in progress (`.specify/specs/<feature>/` exists) and
+the user invoked `/fact-start` anyway, suggest `/fact-next` as an alternative.

fact/_data/commands/fact-status.md

@@ -0,0 +1,30 @@
+---
+description: Print a quick status report — phase, tasks, last activity, next step.
+---
+
+Print a project status summary in chat. Be concise (10 lines max).
+
+Read only headers / metadata, not full files:
+
+- Project type (greenfield / brownfield / demo) — infer from
+  `.specify/specs/` structure or prior session summaries.
+- Active feature (most recently modified subdir of `.specify/specs/`).
+- Current phase (which files exist: constitution / spec / plan / tasks).
+- Tasks: `<done>/<total>` parsed from `tasks.md`.
+- Last activity: `updated_at` from `.specify/fact/session_state.json`, or the
+  most recent file in `.specify/fact/sessions/`.
+- Next recommended step in one line.
+
+Suggested format:
+
+```
+Project:    <name>  •  <type>
+Phase:      <phase>
+Feature:    <slug>
+Tasks:      <done>/<total>  ([x] T-007 last done)
+Last act:   <iso>
+Next:       <one line>
+```
+
+Do not open large files. If something can't be determined, show `?` — never
+fabricate (P10).