Commit 72275696 authored by Jan Reimes's avatar Jan Reimes
Browse files

feat(specs): implement crawl and query commands for 3GPP specifications 

- Add `crawl-specs` command to fetch metadata from 3GPP.org and whatthespec.net.
- Introduce `query-specs` command for searching the local spec catalog.
- Implement `checkout-spec` and `open-spec` commands for document retrieval.
- Create data models for specifications, source records, versions, and downloads.
- Establish a structured implementation plan and quality checklist for specs.
parent 357e1e54

.beads/export-state/84f3ec93c610dda5.json

0 → 100644
+6 −0
Original line number Diff line number Diff line 
{

  "worktree_root": "D:/SVN/Projects/Standardization/tdoc-crawler.worktrees/copilot-worktree-2026-02-05T11-45-14",

  "last_export_commit": "6f74ac8299d4f1c43a7dcc82d39f69e492d5d247",

  "last_export_time": "2026-02-05T12:45:17.4420916+01:00",

  "jsonl_hash": "4805f8d70b5bb2aac48610ca5837e4449c04a11d9434b6d14a85dabab0e0db15"

}
 
 No newline at end of file

.beads/export-state/cb201b3a15cb4cec.json

0 → 100644
+6 −0
Original line number Diff line number Diff line 
{

  "worktree_root": "D:/SVN/Projects/Standardization/tdoc-crawler",

  "last_export_commit": "6f74ac8299d4f1c43a7dcc82d39f69e492d5d247",

  "last_export_time": "2026-02-05T02:48:04.4458383+01:00",

  "jsonl_hash": "4805f8d70b5bb2aac48610ca5837e4449c04a11d9434b6d14a85dabab0e0db15"

}
 
 No newline at end of file

.gitignore

+1 −0
Original line number Diff line number Diff line
@@ -224,3 +224,4 @@ __marimo__/ 
.opencode/command/speckit.*

nul

.sisyphus

/.github
 
 No newline at end of file

pyproject.toml

+1 −0
Original line number Diff line number Diff line
@@ -28,6 +28,7 @@ dependencies = [ 
    "rich>=14.2.0",

    "typer>=0.19.2",

    "xlsxwriter>=3.2.9",

    "zipinspect>=0.1.2",

]



[project.urls]

specs/001-specs-crawl-query/checklists/requirements.md

0 → 100644
+36 −0
Original line number Diff line number Diff line 
# Specification Quality Checklist: Crawl and Query Specs



**Purpose**: Validate specification completeness and quality before proceeding to planning

**Created**: 2026-02-05

**Feature**: [specs/001-specs-crawl-query/spec.md](specs/001-specs-crawl-query/spec.md)



## Content Quality



- [X] No implementation details (languages, frameworks, APIs)

- [X] Focused on user value and business needs

- [X] Written for non-technical stakeholders

- [X] All mandatory sections completed



## Requirement Completeness



- [X] No [NEEDS CLARIFICATION] markers remain

- [X] Requirements are testable and unambiguous

- [X] Success criteria are measurable

- [X] Success criteria are technology-agnostic (no implementation details)

- [X] All acceptance scenarios are defined

- [X] Edge cases are identified

- [X] Scope is clearly bounded

- [X] Dependencies and assumptions identified

- [X] Command options cover release selection and doc-only behavior



## Feature Readiness



- [X] All functional requirements have clear acceptance criteria

- [X] User scenarios cover primary flows

- [X] Feature meets measurable outcomes defined in Success Criteria

- [X] No implementation details leak into specification

- [X] All new commands are represented in functional requirements



## Notes



- Items marked incomplete require spec updates before `/speckit.clarify` or `/speckit.plan`