docs(openspec): plan hackathon-analysis change - #19
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Planning artifacts for change 3,
hackathon-analysis. No code.A team can analyze a hackathon page from the group's general chat, and later pin that analysis in the hackathon's forum topic:
/hackathon <url>(admin-only) queues a new analysis./hackathon <slug>re-shows an analysis. When an admin runs it inside a topic, it also links and pins the analysis there./hackathonslists the team's analyses.vars.max_concurrency: 1) runs the analysis and posts or pins the result. Jobs are tracked by id so a redelivered message is not processed twice./linkrepo.Size exception: about 980 lines, all documentation.
Files
openspec/changes/hackathon-analysis/explore.md,proposal.md,design.md,tasks.mdopenspec/changes/hackathon-analysis/specs/{hackathon-analysis,page-fetch,llm-extraction}/spec.mdDelivery plan
Ten PRs to
main, in this order:The operator steps are tracked in
tasks.mdPhase 11: create the queue, enable the AI and Browser bindings, give the bot pin rights, and verify the model IDs.🤖 Generated with Claude Code