Advanced and Deep effort levels lack 'When' criteria
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 72/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Stale
- Domain
- documentation
Research direction
Open versions/TheAlgorithm_Latest.md around lines 40-41 and review the effort-level table, especially Advanced and Deep. Add distinct When criteria consistent with the issue's suggested scope; done means both tiers have non-overlapping guidance and the table remains correctly formatted.
Written by the indexing model from the issue text.
Description
The Issue
The effort level table in OBSERVE defines 8 tiers, but Advanced and Deep have no guidance on when to use them:
| Tier | Budget | When |
|---|---|---|
| Instant | <10s | "right now", trivial lookup, greeting |
| Fast | <1min | "quickly", simple fix, skill invocation |
| Standard | <2min | Normal request, no time pressure stated |
| Extended | <8min | Still needed relatively fast, but quality must be extraordinary |
| Advanced | <16min | (no "When" criteria — description same as Deep) |
| Deep | <32min | (no "When" criteria — description same as Advanced) |
| Comprehensive | <120m | Don't feel rushed by time |
| Loop | Unbounded | External loop, PRD iteration |
Both Advanced and Deep have identical descriptions: "Full phases, checkpoints every 1 min" — making it impossible to distinguish when one should be selected over the other.
Suggested Fix
Add "When" guidance. For example:
- Advanced: "Multi-system changes, cross-cutting concerns, significant refactors"
- Deep: "Architectural decisions, novel problem domains, research-heavy work"
Location
- Lines ~40-41 in
versions/TheAlgorithm_Latest.md
- Dominant language
- No language data
- Stars
- 158
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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 danielmiessler/TheAlgorithm
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
danielmiessler/TheAlgorithm#8 · 1 reaction ·
-
Difficulty 1/5 Under an hour Newbie friendliness 48/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 48/100
All issues in danielmiessler/TheAlgorithm
Similar issues
-
triage
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
feature pydanty:is-working
Difficulty 1/5 Under an hour Newbie friendliness 88/100
pydantic/pydantic-ai#8647 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
:watch: Not Triaged dotnet-fsharp/svc
Difficulty 1/5 Under an hour Newbie friendliness 90/100