Opensrc Knowledge Refactor Backlog
Opensrc Knowledge Refactor Backlog
Source requirements:
Provider payloads: not generated; no issue provider was requested.
Linear sync:
Delivery artifacts:
- Spec:
apps/wiki/specs/cli/IP-157-curated-opensrc-example-repositories/SPEC.md - Plan:
apps/wiki/specs/cli/IP-157-curated-opensrc-example-repositories/PLAN.md
Module: Scaffold Knowledge Context
The scaffold system should distinguish direct package source inspection from curated example repository context supplied by framework packs.
Epic: Curated Opensrc Example Repositories For Framework Packs
Outcome:
Framework packs can declare maintainer-curated example repositories. Generated scoped prompt guidance can then tell agents to inspect those examples with opensrc when the pack applies to that scope.
Scope:
- Model curated example repositories as pack-owned metadata.
- Keep example repository entries minimal.
- Seed the Effect pack with the manually selected repositories from the grill.
- Surface selected-pack examples in scoped/workspace prompt guidance.
- Preserve the rule that scaffold setup must not invent arbitrary
opensrcrepositories.
Cross-story constraints:
- Example repositories are evidence sources for real-world patterns and code architectures aligned with the pack's included skills.
- Repository inclusion is maintainer curation, not a validation gate.
- Versions must come from cloned example repository manifests.
- Root shared guidance remains generic; concrete example repository lists belong to selected-pack scoped guidance.
Story 1: Pack Catalog Carries Curated Example Repositories
Outcome: The scaffold catalog can represent curated example repositories attached to one or more packs.
Acceptance signals:
- Each example repository records only
repo,url, andpacks. - Each
packsentry records{ uid, version }. - The model does not add per-repository
why,inspectFor,avoidUsingFor, or unknown-version fallback fields. - Catalog consumers can read example repository metadata from the same pack source of truth as skills, prompt surfaces, hooks, and lint metadata.
Story 2: Effect Pack Includes The Seed Example Repositories
Outcome: The Effect pack exposes the selected example repositories as curated opensrc context.
Acceptance signals:
- The Effect pack includes
AnswerOverflow/AnswerOverflow. - The Effect pack includes
rhyssullivan/executor. - The Effect pack includes
alchemy-run/alchemy-effect. - The Effect pack includes
anomalyco/opencode. - The Effect pack includes
pingdotgg/t3code. - Each repository's Effect version is read from its cloned repository manifest before finalizing the catalog entry.
Blocked by:
- Story 1.
Story 3: Scoped Prompt Guidance Emits Selected-Pack Examples
Outcome:
Generated scoped/workspace prompt specs include explicit opensrc guidance for curated examples when a selected pack contributes those examples to the scope.
Acceptance signals:
- Scoped guidance tells agents to inspect curated examples with
opensrc path owner/repo. - Guidance explains that examples are for gathering real-world patterns and code architectures aligned with the pack's included skills.
- Root shared guidance stays generic and does not list every concrete example repository by default.
- Scaffold setup still does not invent or auto-select arbitrary repositories outside maintained pack metadata.
Blocked by:
- Story 1.
- Story 2.
Story 4: Documentation Captures The Refined Opensrc Contract
Outcome: Human-facing requirements and wiki/project context describe the two opensrc contexts without claiming the implementation already exists.
Acceptance signals:
- Requirements docs distinguish package source context from curated example repository context.
- Project context links the grill and backlog artifacts.
- Wiki scaffold-pack knowledge explains that packs may own curated example repositories.
- Current-behavior runbooks are updated only after implementation changes land.
Blocked by:
- Story 1.
Deferred Scope
- Non-Effect framework packs are parked until a maintainer selects their curated example repositories.
- Provider-specific issue creation payloads are parked until a target provider is requested.