feat: initialize typescript project by TabishB · Pull Request #1 · Fission-AI/OpenSpec

TabishB · 2025-08-05T12:31:58Z

Summary

Set up TypeScript project with ESM module support
Created initial CLI structure with commander.js
Added OpenSpec documentation clarifications for infrastructure changes

Test plan

Verify TypeScript builds successfully: pnpm build
Test CLI runs: node bin/openspec.js --help
Confirm all tasks marked complete and change archived

Based on OPENSPEC_COMPREHENSIVE_RETROSPECTIVE.md analysis: Added critical missing documentation: - Scenario formatting requirements (#### Scenario: headers) - #1 pain point - Complete spec file structure examples with ADDED/MODIFIED sections - Delta file location and extraction explanation - Debugging commands (show --json --deltas-only) - Troubleshooting section with common errors and solutions Expanded implementation: - Added 2 new task sections (Spec File Documentation, Troubleshooting) - Increased from 41 to 52 total implementation tasks - Added critical items to CLAUDE.md template tasks This directly addresses the retrospective's top issues: 1. Scenario format documentation (marked "COMPLETELY MISSING") 2. Complete spec file examples 3. Delta detection debugging 4. Silent parsing failure explanations

feat: initialize typescript project

Based on OPENSPEC_COMPREHENSIVE_RETROSPECTIVE.md analysis: Added critical missing documentation: - Scenario formatting requirements (#### Scenario: headers) - Fission-AI#1 pain point - Complete spec file structure examples with ADDED/MODIFIED sections - Delta file location and extraction explanation - Debugging commands (show --json --deltas-only) - Troubleshooting section with common errors and solutions Expanded implementation: - Added 2 new task sections (Spec File Documentation, Troubleshooting) - Increased from 41 to 52 total implementation tasks - Added critical items to CLAUDE.md template tasks This directly addresses the retrospective's top issues: 1. Scenario format documentation (marked "COMPLETELY MISSING") 2. Complete spec file examples 3. Delta detection debugging 4. Silent parsing failure explanations

Adds two change proposals for implementing Slice 3 of the artifact POC: 1. restructure-schema-directories - Move schemas from embedded TS objects to self-contained directories - Each schema becomes a directory with schema.yaml + templates/ - Enables co-located templates for user extensibility - 2-level resolution: user override → package built-in 2. add-instruction-loader (depends on #1) - Load templates from schema directories - Enrich templates with change context (dependencies, next steps) - Format change status for CLI output - New instruction-loader capability These proposals complete Slice 3 from docs/artifact_poc.md.

* proposal: add instruction loader and schema restructure (Slice 3) Adds two change proposals for implementing Slice 3 of the artifact POC: 1. restructure-schema-directories - Move schemas from embedded TS objects to self-contained directories - Each schema becomes a directory with schema.yaml + templates/ - Enables co-located templates for user extensibility - 2-level resolution: user override → package built-in 2. add-instruction-loader (depends on #1) - Load templates from schema directories - Enrich templates with change context (dependencies, next steps) - Format change status for CLI output - New instruction-loader capability These proposals complete Slice 3 from docs/artifact_poc.md. * fix: include full requirement block in MODIFIED spec Update the Schema Loading requirement to include all original scenarios (modified as needed) per the MODIFIED requirement guidelines. The archiver replaces the entire requirement with the provided content.

…ssion-AI#410) * proposal: add instruction loader and schema restructure (Slice 3) Adds two change proposals for implementing Slice 3 of the artifact POC: 1. restructure-schema-directories - Move schemas from embedded TS objects to self-contained directories - Each schema becomes a directory with schema.yaml + templates/ - Enables co-located templates for user extensibility - 2-level resolution: user override → package built-in 2. add-instruction-loader (depends on Fission-AI#1) - Load templates from schema directories - Enrich templates with change context (dependencies, next steps) - Format change status for CLI output - New instruction-loader capability These proposals complete Slice 3 from docs/artifact_poc.md. * fix: include full requirement block in MODIFIED spec Update the Schema Loading requirement to include all original scenarios (modified as needed) per the MODIFIED requirement guidelines. The archiver replaces the entire requirement with the provided content.

remove PostHog telemetry completely

…ssion-AI#410) * proposal: add instruction loader and schema restructure (Slice 3) Adds two change proposals for implementing Slice 3 of the artifact POC: 1. restructure-schema-directories - Move schemas from embedded TS objects to self-contained directories - Each schema becomes a directory with schema.yaml + templates/ - Enables co-located templates for user extensibility - 2-level resolution: user override → package built-in 2. add-instruction-loader (depends on #1) - Load templates from schema directories - Enrich templates with change context (dependencies, next steps) - Format change status for CLI output - New instruction-loader capability These proposals complete Slice 3 from docs/artifact_poc.md. * fix: include full requirement block in MODIFIED spec Update the Schema Loading requirement to include all original scenarios (modified as needed) per the MODIFIED requirement guidelines. The archiver replaces the entire requirement with the provided content.

remove PostHog telemetry completely

Flesh out the shorthand backlog entry on reducing git prompts into a full-context idea matching the format of #1–#17, grounded in the actual prompt surfaces in the tier skills and the finishing-a-development-branch handoff. Calls out concrete defaults, an opt-out lever, and cross-refs to ideas #3, #6, and #16. Co-authored-by: Cursor <cursoragent@cursor.com>

Deterministic, enforced counterpart to the prompt-level ADR drift hint (the real fix vs a model hint). New extensible mechanism: - src/core/lint/: LintRule/LintFinding/LintContext types + a rule registry (ALL_RULES). runLint(projectRoot, opts) resolves the ADR dir and runs selected rules. - rule #1 adr-registry: pure checkAdrRegistry({adrs,errors,registryContent, adrDirExists}) -> findings (TDD'd red-first): registry missing -> error; drift vs frontmatter -> error; malformed ADR -> error; no ADR dir -> skip. Reuses scanAdrDir + renderRegistry. - command `openspec lint [--adr] [--adr-dir <path>] [--json]`; exits non-zero on any error finding (CI/hook-ready). + completion registry entry. Future rules (Files-to-Change exist, design Open-Questions gate — the deferred B/C work) slot into ALL_RULES. 9 new tests; suite 1700/1700. No template changes -> no parity re-harvest.

The change-gate agent runs the FULL gate (vitest-all + coverage + Playwright e2e) inside its own turn → blows the claude-terminal turn cap (live run: all 5 waves green, then change-gate timed out). Violates Archon good-practice #1 (deterministic work belongs in bash, not the AI). Fix (do after the current run): move the gate RUN to until_bash/bash (captures failures to an $ARTIFACTS_DIR file, no agent-turn cap); the agent loop only FIXES the captured failures (bounded turn). Loop exposes no until_bash-output var (only LOOP_PREV_OUTPUT/LOOP_USER_INPUT), so failures pass via file. Generalizes: deterministic test runs in bash, agent only fixes — default for all gate/fix loops.

handoff-tail-restructure.md carries the next build session's prompt (close the last v1 bar + change-gate turn-cap): edit the lexup generator, the 5-item punch list (§14/§15/§16.4), gotchas (worktree config load, resume-by-run-id, turnTimeoutMs back to 900000 since the restructure removes the band-aid). README open-stack #1 points to it.

…ot (§16.5) Mark the §16.4 tail-restructure punch list DONE (lexup dev 84a0ea2a). New §16.5 records what was built and the one forced mechanism change: the archon loop's until_bash hook is hardcapped at 120s (dag-executor.ts:2470, no node.timeout), too short for the Playwright e2e gate — so the loop is infeasible for a slow gate. The change-gate is therefore UNROLLED bash gate-run + agent fix slots (the harness idiom, the note's sanctioned "preceding bash step"), which keeps §14's principle (gate in bash, agent only fixes) intact. Also records: forked opsx-* base-diff review commands emitted from the generator (decision 16 single-source), the create-pr-on-red policy + 3-state report, and stub-probe verification of the gate cascade. Archon follow-up noted (make until_bash honor node.timeout). Open stack #1 → BUILT; handoff → DONE.

… + report-only dispatched mode (grills adaptation layer) Closes the gap where expert skills (review/cso/qa/qa-only/benchmark/ design-review) had no distinct behavior when invoked by the LEAD as a dispatched, report-only single-unit-of-work vs. standalone interactive use — dispatched runs could still trigger fix loops, AskUserQuestion, git commit, or subagent spawns that belong only to standalone mode. - Canonical B/Ma/Mi/T severity vocabulary + per-expert mapping table in the shared PREAMBLE (_shared.ts), translating each expert's native scale (review CRITICAL/INFORMATIONAL, cso CRITICAL/HIGH/ MEDIUM, qa/qa-only critical/high/medium/low/cosmetic, benchmark REGRESSION/WARNING/OK+Grade, design-review impact+Grade, codex P1/P2) into canonical, with "finding content overrides native label" as the tiebreak rule. - Dispatched vs standalone mode contract: trigger signature (single-unit-of-work + no-subagents + LEAD-owns-orchestration, or explicit MODE token); dispatched mode forbids AUTO-FIX, AskUserQuestion, git commit, and subagent dispatch, with a global override clause; denied-edit honesty clause (freeze/guard-denied edit reported as [BLOCKED], never [AUTO-FIXED]). - Mode-gated mutating steps: review's Fix-First AUTO-FIX + batched/ Greptile AskUserQuestion + two-axis parallel Agent workers; ADVERSARIAL_STEP subagent dispatch; TEST_COVERAGE_AUDIT_REVIEW generate/run/commit (including its REGRESSION IRON RULE, fixed in round 1 to carry its own dispatched clause); qa's and design-review's clean-tree gate + fix loop + per-fix commit; cso's Phase 7 Remediation Roadmap AskUserQuestion. - Report-file contract reconciled: dispatched mode writes canonical <skill>-report.md in the change dir with canonical severities; standalone keeps native paths unchanged. _orchestration.ts Step B sentence rewritten — dropped the inaccurate "save NOTHING" claim; dispatched experts write the report themselves, worker verifies presence (no double-write). - RV-8 cso probe/exclusion alignment: narrowed hard-exclusion #1 to generic DoS with an explicit auth/security-endpoint brute-force exception (kept the A04 rate-limit probe); dropped the A09 audit-logging probes; resolves a prior probe-vs-exclusion self-contradiction. Installed skills regenerated via `node build.js` (pnpm build currently broken by a concurrent session's in-flight pnpm-workspace.yaml — confirmed identical output via direct node build.js). Parity hashes resynced for the 14 PREAMBLE-embedding templates. Reviewed CLEAN (review-cycle round 1, non-author confirmed): 1 Minor + 1 Trivial fixed, 2 accepted-known (chrome-use parity blind spot, pre-existing; cross-session getOpsx hash bundling, see below). Two deliberate bundlings, both LEAD-ruled accepted (documented in ship-log.md): 1. The 8 source files carry in-flight openspec->rasen branding edits at whole-file granularity from a concurrent rebrand session; the migration itself is delivered separately. 2. skill-templates-parity.test.ts additionally carries 11 getOpsx*CommandTemplate hash lines adopted by the rebrand session directly in the shared tree (not this change's work — import-graph confirms command templates don't consume PREAMBLE/_orchestration); co-committed because the hash-constant file must be internally self-consistent against the live tree for the suite to pass. The rebrand session's own ship supplies the matching template content. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

Moves the completed prompt-audit-fixes-expert-dispatch change (child #1 of the prompt-audit-fixes portfolio) to rasen/changes/archive/2026-07-09-prompt-audit-fixes-expert-dispatch/ and syncs its three delta specs as new capabilities in rasen/specs/: - canonical-severity-vocabulary: Blocker/Major/Minor/Trivial as the single canonical severity scale plus the per-expert mapping table, carried in the shared PREAMBLE and self-applied by experts in dispatched mode. - cso-finding-scope: cso Phase 2 assessment probes agree with Phase 5 hard exclusions (auth brute-force reportable, generic DoS excluded, audit-logging probe dropped). - expert-dispatch-contract: the dispatched vs standalone mode contract for generic expert skills (review/cso/qa/qa-only/benchmark/ design-review) — report-only gating, canonical report-file convention, denied-edit honesty. Note on pathspec precision: rasen/specs/ was staged with ~98 entries from the concurrent openspec->rasen rebrand session at commit time (since committed separately as 2ebfae9); staged the three new spec subdirectories individually rather than the rasen/specs/ parent to avoid sweeping in that unrelated staged content. All 28/28 tasks complete; all 4 artifacts done; all three synced specs validate clean (`rasen spec validate`). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

…onical VERIFY VERDICT, tree-fingerprint evidence, never-read-source scoping Closes the gap where verify-change and verify-enhanced computed a verdict but never persisted a machine-checkable evidence artifact, so ship's pre-flight test-skip gate had no canonical verify output to key off, and the verify-family's severity classifications weren't tied to child #1's canonical vocabulary. Also closes a "never read source code" absolute-without-scope gap in the shared QA/DESIGN methodology blocks, and a pre-existing chrome-use parity coverage gap. - WF-1 (evidence file + ship pre-flight wiring): verify-change.ts (both skill and command getters) adds a Save Report step writing rasen/changes/<name>/verification-report.md with the summary scorecard, verdict status line, and grouped findings. - WF-7 (verdict unification, consumes canonical-severity-vocabulary): verify-change maps CRITICAL/WARNING/SUGGESTION and verify-enhanced maps Critical Issues/Warnings/per-stage PASS-FAIL onto canonical Blocker/Major/Minor/Trivial by reference (no re-declaration); per-stage PASS/FAIL kept as a display aid in verify-enhanced. - WF-8 (test-evidence chain): both verify getters emit the machine-checkable "VERIFY VERDICT: <CLEAN|BLOCKED> — Blocker:<n> Major:<n> Minor:<n> Trivial:<n>" status line (CLEAN iff no open Blocker/Major) and record a tree-fingerprinted test-evidence block (command(s) + result + git rev-parse HEAD^{tree}) when they run any test/gate command, matching the review-cycle schema. ship.ts adds verification-report.md to the pre-flight verification-evidence list and names it explicitly in the test-skip gate's evidence sources (skip-gate logic itself unchanged). - SH-1/SH-2 + RV-6/RV-7 (enumerate-and-gate scoping): _shared.ts QA_METHODOLOGY (#5/#7) and DESIGN_METHODOLOGY (#4) "never read source code" absolutes scoped to the exploration/testing/audit phase, with an explicit carve-out naming (a) diff-aware triage and (b) the STANDALONE fix loop — does not reopen child #1's dispatched-mode report-only contract. - D5: chrome-use added to the parity table (functionFactories + GENERATED_SKILL_FACTORIES + both hash maps), closing a pre-existing blind spot noted in the office-hours-dialogue-override review. Installed skills regenerated via node build.js (pnpm build still broken by the in-flight pnpm-workspace.yaml — confirmed identical output). Parity hashes resynced for qa, qa-only, design-review, plus the new chrome-use entries; verified no other template's hash moved. Reviewed CLEAN (review-cycle round 1, non-author confirmed): 1 Minor fixed (verify-change's Save-Report prose falsely claimed /rasen:retro reads verification-report.md — retro.ts's Outcome Artifacts list never enumerates it; trimmed the false claim, /rasen:ship — the real, correctly-wired consumer — remains named), 2 Trivial accepted-known (qa-only carve-out clause (b) references a fix loop qa-only doesn't have, harmless since it only permits; verify-enhanced omits restating "content overrides label" inline, relying on the referenced canonical-severity-vocabulary instead — acceptable by-reference pattern). ship.ts/verify-enhanced.ts absence from the parity registry (they're commands, not templates) is a pre-existing scope gap, not introduced here — relayed to child #3/#5 if in scope there. No whole-file branding-bundling residue this ship: unlike child #1 (which landed mid-rebrand), the rebrand session's openspec->rasen rename is already committed (2ebfae9, ca54b3b), so these 5 files carry no in-flight branding churn — no LEAD ruling needed here. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

…evival, two-threshold rule, counter disambiguation Closes a family of ambiguities in the LEAD orchestration playbook (_orchestration.ts, auto.ts, goal-command.ts) around worker death, threshold counters, and gate semantics — cases where the same-sounding number or event was governed by two different rules depending on context, with no explicit disambiguation. - OR-1/SH-4 threshold families: relay caps, stall limits, and round caps disambiguated — each named explicitly and scoped to the lifecycle event it governs. - H.4/OR-6 worker-death taxonomy + infra revival: two-branch taxonomy — (a) genuine work-exhaustion (HANDOFF) vs (b) infrastructure death (process/connection failure). An infra-death SendMessage-triggered revival is NOT charged against the relay/ stall caps that govern (a). The (a)-vs-(b) boundary has a documented residual ambiguity, accepted in design Risks as cheap/self-correcting (a genuinely-full worker HANDOFFs on the wake turn and gets reclassified). - OR-9/OR-13/OR-15 counter disambiguation: a counter table maps every counter token (maxRelays, stallLimit, maxRounds, loop.maxRounds, strategyAttempts, loopStallLimit, sessionHandoff.n) to its exact governing rule — grep-audited, no orphans. - Tier-C degradations (OR-4, OR-14): LEAD never self-certifies a Tier-C implementer's work without an independent check. verifyPolicy standard/light modes defined in auto.ts section 5 (verify stages only run under the auto command). - OR-8/OR-11/SH-5/SH-7: SH-5 scopes the LEAD's "flag it" duty — an out-of-scope issue the LEAD notices routes to DONE durable-findings, not autonomous investigate/fix/ask-user; explicitly disclaims reopening child #1's dispatched-mode report-only contract. SH-7 defines a narrow inline-fix exception. - Gate directive precedence (D6, LEAD ruling): Step G resolves how a decomposed portfolio's child-pipeline gates behave with no explicit parent gate directive — default is auto-continue (record the checkpoint, do not pause per child), since irreversible actions already collapse to the single portfolio-level delivery decision. Reversible product decision, surfaced to the user in the ship log rather than silently baked in. Round 2 tightened Step G's prose after the reviewer flagged that the wording could be misread as the opposite default — behavior unchanged, wording clarified. _orchestration.ts/auto.ts/goal-command.ts are NOT in the parity golden-master registry (pre-existing gap). Verified instead via node build.js + node dist/cli/index.js update succeeding, plus 5 independent grep spot-checks against the regenerated rasen-auto/ rasen-review-cycle/commands-auto output confirming the new prose is present verbatim, performed independently by implementer and reviewer. Registry expansion relayed to child #5 (prompt-audit-fixes-lifecycle), along with a newly-discovered, distinct gap: rasen-goal/goal-plan templates are absent from the generation registry entirely, not just the parity registry. Installed skills regenerated via node build.js. Parity hashes resynced for the 15 PREAMBLE-importing expert templates (careful/freeze/guard/unfreeze correctly show zero movement — they do not import PREAMBLE; a task-note miscount of "19" was corrected to 15 in fix round 1). Reviewed CLEAN APPROVED (review-cycle, 2 rounds, non-author confirmed). Round 1: 1 Minor fixed (auto.ts's gate guardrail lacked a back-reference to Step G's precedence rule — added a scoped cross-reference), 1 Trivial fixed (tasks.md miscounted PREAMBLE embedders as 19, corrected to 15). Round 2: 1 new Minor found and fixed (Step G sentence 1's "does NOT suppress ... by default" wording could be misread as contradicting the D6 auto-continue default — tightened without changing behavior). Seam integrity confirmed: child #1's Step B report-contract sentence and child #2's verify/ship evidence chain both verified untouched by this diff. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

…er, archive hard gates, delivery preconditions, F.1 generation-match Wires the propose/office-hours/archive/apply/continue workflow commands into the evidence chain and gates established by children #1-#3, and closes a resume-ladder generation-match gap in orchestration. - WF-2: propose.ts checks both office-hours-design.md (change dir) and the sibling office-hours directory (by slug) before drafting, incorporating found validation and naming office-hours as the source; all paths resolved from status JSON. office-hours.ts's producer-side notes (dual-write, auto-detect, downstream integration) made accurate to match, with a verbatim slug-derivation example matching propose's so the two-sided derivation converges (fixed in round 1 after the reviewer caught divergent examples). - WF-6: office-hours.ts (workflow command) restructured so the /office-hours expert is the single facilitation authority; the inline six-questions/builder text becomes an explicit fallback pre-brief, not a second pass; doc production consolidated to one step; precedence stated. - WF-4: archive-change.ts gates on verification-report.md's VERIFY VERDICT (child #2's evidence file) -- refuses by default on BLOCKED, requires an explicit blocker-naming override, refuses outright non-interactively; CLEAN passes with no gate; absence gets a soft note only. Incomplete-tasks check elevated from soft warning to the same hard-gate semantics. The "don't block on warnings" guardrail re-scoped (enumerate-and-gate) to soft warnings only, explicitly excluding both new hard gates. - WF-5/WF-11: archive-change.ts adds a delivery-precondition check reading ship-log.md (soft warning if absent, with a spec-only escape) and a portfolio-awareness note when the ship log's Status line reads "delivery deferred to portfolio level" (ship.ts's exact local-mode marker). - WF-5 (apply) / WF-10 (continue): completion nudges in apply-change.ts and continue-change.ts steer through /rasen:verify -> /rasen:ship, naming archive only as the post-delivery step rather than an immediate co-equal option. - F.1 (LEAD-added, _orchestration.ts scope exception -- one clause, nothing else touched, children #1/#3's edits survive byte-for-byte): Step F.1's resume ladder now states a handoff document counts only if it's the LATEST holder's own distillation; an un-exhausted latest holder with no document resumes from its TRANSCRIPT instead, which beats any earlier generation's document. Adds the same-session- restart nuance: SendMessage-by-NAME may still resolve the latest holder post-restart -- try that wake first, fall back to the ladder otherwise. This exact behavior was live-validated during this change's own implementation (see ship-log's Infra-Revival section). - Parity registry expansion: +19 function-hash entries + 11 content-hash entries for the previously-unpinned workflow/command family (office-hours-command, verify-enhanced, ship, retro, auto, review-cycle, handoff, goal-plan/iterate/report/command) -- this is what makes the F.1 edit verifiable, since it hash-locks rasen-auto/rasen-goal/rasen-review-cycle for the first time. Reviewed CLEAN (review-cycle round 1, non-author confirmed): 1 Minor fixed (propose/office-hours slug-example divergence), 1 Minor accepted-known (F.1's hash movement can't be diff-verified against a pre-edit baseline since the templates were pinned in the same regen run as the edit -- D8, inherent to prior parity debt, not a defect), 2 Trivial accepted-known and skipped by design (office-hours wording nuance deferred to child #6's WF-3; F.1 clause density -- tightening declined to avoid re-churning newly-locked hashes for zero functional gain). Seam integrity confirmed byte-compatible both directions against the actual producer strings, called out by the reviewer as "the opposite of the WF-1 disease" this portfolio exists to close. Infra-revival event during fix round 1: implementer's connection closed mid-edit; LEAD applied child #3's H.4(b) protocol (SendMessage-revive the same agent, zero rework since edits had already landed) rather than cold-reconstructing -- not charged to relay/stall budget, and incidentally a live validation of this change's own F.1 same-session-restart nuance before its hash-lock even shipped. Known-open item relayed to the portfolio-end report (not this change's scope): goal templates are registered in the generation registry, but `update` still doesn't emit rasen-goal* skill directories -- suspected deploy-path filter, not root-caused. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

TabishB added 3 commits August 5, 2025 22:29

feat: initialize typescript project with esm support

d94f4fb

chore: archive completed typescript initialization change

48ad6c5

chore: add dev:cli script and enhance package files config

fdf0514

TabishB merged commit ed04971 into main Aug 5, 2025

TabishB mentioned this pull request Aug 25, 2025

Update OpenSpec agent instructions for clarity and completeness #50

Merged

4 tasks

drvova pushed a commit to drvova/VovaSpec that referenced this pull request Oct 13, 2025

Merge pull request Fission-AI#1 from Fission-AI/project-setup

93b2bac

feat: initialize typescript project

coderabbitai Bot mentioned this pull request Nov 2, 2025

feat: add Qwen Code support with slash command integration #250

Merged

TabishB mentioned this pull request Dec 26, 2025

proposal: add instruction loader and schema restructure (Slice 3) #410

Merged

3 tasks

greptile-apps Bot mentioned this pull request Jan 23, 2026

feat(cli): merge init and experimental commands #564

Merged

3 tasks

evilsamaritan mentioned this pull request Jan 29, 2026

Nested Specs #594

Closed

1code-async Bot mentioned this pull request Feb 18, 2026

Improve explore → change transition guidance in skills #720

Closed

1code-async Bot mentioned this pull request Feb 23, 2026

Extension for SpecKit #750

Closed

SWolfeCAI referenced this pull request in AnchorSpec/AnchorSpec Mar 27, 2026

Merge pull request #1 from Steven-Wolfe/telemetry-removal

4ed4a6b

remove PostHog telemetry completely

StevenWolfe referenced this pull request in AnchorSpec/AnchorSpec Mar 27, 2026

Merge pull request #1 from Steven-Wolfe/telemetry-removal

0a11d8a

remove PostHog telemetry completely

fsmw mentioned this pull request Jul 3, 2026

[Proposal] Automatic spec catalog discovery during proposal creation #901

Open

Navigation Menu

Uh oh!

feat: initialize typescript project - #1

feat: initialize typescript project#1
TabishB merged 3 commits into
mainfrom
project-setup

TabishB commented Aug 5, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

Conversation

TabishB commented Aug 5, 2025

Summary

Test plan

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant