spec-kitty / spec-kitty/spec-kitty

Monorepo preparation does not include repositories required by downstream mission-review gates

Open
#2,704 3 comments 0 reactions 0 assignees View on GitHub
catfooding priority:P2 reliability workflow
Dominant language
Python
Stars
1.6k
Forks
165
Avg merge
14h 52m
Merged PRs (30d)
303

Description

Observed while preparing the #2658 workspace (TF-052).

## Reproduction

1. Use the supported monorepo-preparation workflow for a Spec Kitty feature and select a workflow that will later run mission review.
2. Observe only the main `spec-kitty` repository is prepared.
3. Reach the mandatory cross-repository E2E gate.
4. Discover `spec-kitty-end-to-end-testing` is absent and must be cloned/configured manually.

## Expected

Preparation should resolve the repository set from selected downstream skills/gates, or preflight should declare the missing sibling before work begins and offer a deterministic add-repository step.

Contributor guide

Open the contributing guide

Research direction

Start with the supported monorepo-preparation workflow and trace how it resolves repositories and downstream skills or gates. Reproduce the #2658/TF-052 scenario through the mandatory cross-repository E2E gate; done means the required sibling is prepared automatically or preflight identifies it and provides a deterministic add-repository step.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
devops, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.