Add a spec-first / scoping workflow guide
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 66/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- github
- Domain
- documentation
Research direction
No files are named. Start by scanning the repository documentation for existing agent-mode and token-budget guidance, then draft a new spec-first/scoping workflow guide in that documentation area. Include the requested points on why scoping lowers correction loops, spec/acceptance criteria, and how to tighten vague tasks, with optional spec-writer guidance. Consider it done when the new guide is added and linked from the docs navigation so it is discoverable and actionable.
Written by the indexing model from the issue text.
Description
Summary
Add a spec-first / scoping workflow guide (and optionally a spec-writer skill). We use AI for well-defined scope; the missing piece is documented discipline for getting to that scope. Spec-first work means fewer correction loops, which means fewer tokens per task — the metric that actually drives cost.
The guide should cover
- Why scoping/spec-first reduces cost (tokens-per-task, not per-token price).
- A practical loop: spec → plan → execute → verify.
- How to write a good spec / acceptance criteria for an agent.
- When a task is too vague to hand to an agent, and how to tighten it.
- Optionally: a
spec-writerskill that helps draft a spec from a rough idea.
Notes
- Back the findings with web research across multiple independent sources.
- Keep it tool-general (GitHub Copilot CLI, OpenCode, Pi).
- Tie in with existing material on agent mode and token budget.
- Dominant language
- Python
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from AbsaOSS/agentic-toolkit
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
AbsaOSS/agentic-toolkit#27 ·
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
AbsaOSS/agentic-toolkit#23 ·
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
AbsaOSS/agentic-toolkit#21 ·
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
AbsaOSS/agentic-toolkit#20 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
AbsaOSS/agentic-toolkit#35 · 1 reaction · 1 assignee ·
All issues in AbsaOSS/agentic-toolkit
Similar issues
-
documentation help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
simonw/sqlite-utils#872 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100