Skip to content

feat: adapt stsTeam plugin to Spec Kit - #1

Open
stswoon wants to merge 1 commit into
mainfrom
feat/speckit-adopt
Open

stswoon wants to merge 1 commit into
mainfrom
feat/speckit-adopt

Conversation

@stswoon

@stswoon stswoon commented Nov 14, 2026

Copy link
Copy Markdown
Owner

Summary

  • Spec Kit-only fork: specs/<NNN-feature>/ (spec.md, plan.md, tasks.md); the old docs/spec + docs/plan mode is removed.
  • Work item = tasks.md phase: FOUNDATION, US1..USn, POLISH, CONV1..N.
  • Cycle: Dev -> QA -> Lead -> Analyst; DONE only after ANALYST_PASS; QA/LEAD/ANALYST failures return to Dev.
  • Parallelism: up to slots items; path, exclusive-path and ui / db / build / codegen resource checks.
  • /speckit.tasks gets the stsTeamPlan parallel slicing pass; /speckit.implement hands the feature to stsTeamImpl; /speckit.converge phases use the same cycle.
  • Integration without editing core Spec Kit: OpenCode V2 prompt hook in plugin.js + speckit.js transformer; on Windows .ps1 calls become .cmd wrappers.

Verification

  • node --test: 21/21.
  • Prompt hook verified end-to-end via OpenCode 2.3.0 API: team mode applied, classic step removed, post hooks preserved, .cmd wrapper applied.
  • Plugin active in family-tree-3; skills, agents and commands registered.

Related

  • family-tree-3 MR !11: plugin wiring (opencode.json).

Do not merge without user review.

Spec Kit-only workflow: tasks.md work items, parallel slots, Dev -> QA -> Lead -> Analyst, Convergence phases and prompt-hook integration without editing core Spec Kit commands.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant