12 KiB
FEATURES
This file is the human-oriented capability map for Singularity Forge.
It is intentionally not the source of truth for schemas or tool parameters. Use it to answer:
- what SF can do today
- which surfaces are first-class versus experimental
- where a capability lives in the system
For exact contracts, use:
README.mdfor product positioning and user docssrc/resources/extensions/sf/workflow-tools.jsfor native workflow tool requirementssrc/resources/extensions/sf/for planning/state-machine behavior and tool schemassrc/resources/extensions/*/extension-manifest.jsonfor extension inventorypackages/pi-ai/src/for provider and model registry behavior
Core Product Shape
SF is a coding-agent application built around:
- a milestone → slice → task planning hierarchy
- a DB-backed workflow state machine
- native SF workflow mutations and readers
- extension-based capability loading
- multi-provider model routing
- interactive and autonomous execution modes
The core planning/runtime loop is:
- discuss / research / align
- plan milestone
- plan slice
- execute task-by-task
- verify gates
- summarize and validate
- reassess roadmap and continue
Planning And Ceremony Capabilities
Milestone planning
SF supports milestone plans with:
- milestone title, vision, and slice breakdown
- success criteria and definition of done
- key risks and proof strategy
- verification contract, integration, operational, and UAT sections
- requirement coverage and boundary-map support
Vision meeting
Milestones can carry a weighted visionMeeting that captures:
pmuserAdvocatecustomerPanelbusinessresearcherdeliveryLeadpartnercombatantarchitectmoderator- weighted synthesis
- confidence by area
- recommended route:
discussing,researching, orplanning
This is the top-level roadmap/vision alignment ceremony.
Slice planning
Slices support:
- goal
- success criteria
- proof level
- integration closure
- observability impact
- ordered task plans with expected files, verification, inputs, outputs
Adversarial review
Slice planning supports first-class adversarial review with:
partnercombatantarchitect
This is treated as required planning structure, not commentary.
Planning meeting
Slices also support a structured planning meeting with:
- trigger
pmresearcherpartnercombatantarchitectmoderator- recommended route
- confidence summary
This is the narrower execution-readiness ceremony.
Replanning
When a blocker invalidates a slice plan, SF supports slice replanning with:
- blocker task + blocker description
- what changed
- updated tasks
- removed tasks
- updated slice-level planning fields
- updated adversarial review
- updated planning meeting
Replan state is preserved in DB and re-rendered into plan artifacts.
Workflow State Machine
The SF workflow engine derives and enforces states including:
pre-planningneeds-discussionplanningevaluating-gatesexecutingsummarizingvalidating-milestonecompleting-milestonereplanning-slicecompleteblocked
Important properties:
- execution readiness is gated by artifact completeness, not just file existence
- meeting/ceremony data participates in readiness
- blocked/dependency-aware progression is built in
- routed-back plans stay in planning instead of pretending to be ready
Artifact And Persistence Capabilities
SF persists workflow state in multiple synchronized forms:
- SQLite DB (
.sf/sf.db) - markdown planning artifacts
- state manifest snapshots
- worktree DB reconciliation state
- workflow events
Planning/ceremony state now survives across:
- DB writes
- markdown rendering
- pure projection rendering
- manifest export / restore
- worktree reconciliation
- state derivation and execution gating
- slice replanning
Execution Capabilities
SF can execute work in:
- interactive mode
- headless mode
- auto mode
- parallel / multi-worker orchestration
Execution-related features include:
- task-sized dispatch units
- crash recovery and lock-aware state
- timeout supervision
- worktree isolation
- per-unit summaries and milestone completion flow
- roadmap reassessment after completed slices
MCP And Workflow Tooling
The workflow layer is exposed over MCP, including mutation/read paths for:
- milestone planning
- slice planning
- slice replanning
- task completion
- slice completion
- milestone validation
- milestone completion
- roadmap reassessment
- gate results
- summary save/read flows
This makes SF usable from external clients without relying on slash-command prompt tricks.
Search And Research Capabilities
SF has dedicated web/research support via onboarding, auth storage, and extension flows.
Currently supported first-class web-search providers include:
bravetavilyserperexa
Other search/research surfaces include:
- Ollama native web search / fetch integration
- Google search extension
- Context7 extension for library/documentation retrieval
- Jina-backed content extraction paths where configured
The search stack is available to automatic workflows, not only slash commands.
Subagents And Background Work
SF includes subagent capabilities via the subagent extension, including:
- delegated agent runs
- background subagent jobs
- await/join behavior
- cancellation
- workflow-driven use rather than only interactive commands
This is useful for automatic coding flows and wave-based task execution.
Extension Inventory
Bundled extension families currently include:
sf— workflow engine, planning/state/artifactssearch-the-websubagentasync-jobsbg-shellbrowser-toolscontext7google-searchollamaremote-questionsslash-commandsmac-toolsttsruniversal-configvoice
These are not all equal in product importance, but they are real shipped extension surfaces.
Model And Provider Capabilities
SF supports multi-provider model routing across built-in and custom providers.
Notable supported/known providers in the current runtime and registry surface include:
anthropicanthropic-vertexopenaiazure-openai-responsesopenai-codexgooglegoogle-gemini-cligoogle-vertexmistralamazon-bedrockollamaollama-cloudopenroutergroqxaigithub-copilotzaiminimaxminimax-cnkimi-codingxiaomicustom-openai
Recent/custom provider support in this tree also includes:
zai/ GLM-family routingxiaomi/ MiMo Anthropic-compatible endpointkimi-coding/ dedicated coding endpointminimaxAnthropic-compatible support
Onboarding And Auth
Onboarding currently supports:
- LLM provider selection
- OAuth or API-key based provider setup where applicable
- local Ollama detection
- web-search provider setup
- remote questions setup
- tool-key collection for selected extensions
This is a real product capability, not just a doc path.
Recovery, Reliability, And Operational Features
SF includes real operational hardening around:
- manifest bootstrapping and restore
- worktree/DB reconciliation
- cache invalidation around plan parsing
- atomic writes and TOCTOU protection
- gate-aware progression
- idle/timeout handling
- scoped recovery for auto mode
UI And Interaction Surfaces
SF is not only a CLI. The repo also carries:
- TUI support
- web interface support
- VS Code extension support
- MCP server support
So the product surface is broader than “terminal prompt framework.”
What This File Does Not Try To Be
This file does not list:
- every MCP tool parameter
- every extension command
- every model ID
- every preference flag
- every internal DB column
Those should stay close to code or generated inventories.
Generated Inventory
The section below is generated from source declarations so this overview can stay concise while exact inventories remain refreshable.
SF Native Tools
Generated from src/resources/extensions/sf/extension-manifest.json.
sf_autonomous_checkpointsf_complete_milestonesf_decision_savesf_execsf_exec_searchsf_graphsf_journal_querysf_log_judgmentsf_milestone_generate_idsf_milestone_statussf_plan_milestonesf_plan_slicesf_plan_tasksf_product_auditsf_reassess_roadmapsf_replan_slicesf_requirement_savesf_requirement_updatesf_resumesf_save_gate_resultsf_self_feedback_resolvesf_self_reportsf_skip_slicesf_slice_completesf_summary_savesf_task_completesf_validate_milestone
Bundled Extensions
Generated from src/resources/extensions/*/extension-manifest.json.
async-jobs— extension-manifest.jsonaws-auth— extension-manifest.jsonbg-shell— extension-manifest.jsonbrowser-tools— extension-manifest.jsonclaude-code-cli— extension-manifest.jsoncontext7— extension-manifest.jsongithub-sync— extension-manifest.jsongoogle-search— extension-manifest.jsonguardrails— extension-manifest.jsonmac-tools— extension-manifest.jsonmcp-client— extension-manifest.jsonollama— extension-manifest.jsonremote-questions— extension-manifest.jsonsearch-the-web— extension-manifest.jsonsf— extension-manifest.jsonsf-inturn-guard— extension-manifest.jsonsf-notify— extension-manifest.jsonsf-permissions— extension-manifest.jsonsf-tui— extension-manifest.jsonsf-usage-bar— extension-manifest.jsonslash-commands— extension-manifest.jsonsubagent— extension-manifest.jsonttsr— extension-manifest.jsonuniversal-config— extension-manifest.jsonvectordrive— extension-manifest.jsonvoice— extension-manifest.json
Search Providers
Generated from the search-the-web extension provider declarations.
braveexaollamaserpertavily
Known Model Providers
Generated from packages/pi-ai/src/types.ts (KnownProvider).
alibaba-coding-planalibaba-dashscopeamazon-bedrockanthropicanthropic-vertexazure-openai-responsescerebrasgithub-copilotgooglegoogle-gemini-cligoogle-vertexgroqhuggingfacekimi-codinglongcatminimaxminimax-cnmistralollamaollama-cloudopenaiopenai-codexopencodeopencode-goopenroutervercel-ai-gatewayxaixiaomixiaomi-token-plan-amsxiaomi-token-plan-cnxiaomi-token-plan-sgpzai