standard(done): a feature is done on every surface of its product — web, admin, mobile, Mac and CLI — or says why not
Maintainers usually reply within 1 day
A pull request for this has already been merged.
- #443 by @krizaka-agents — merged
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 15/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- github-actions
- Domain
- documentation
Research direction
PR #443 is merged, so review it first. The standard belongs in docs/standards/surfaces.json; then update feature issue template and org workflow to require per-surface ticks. Done means a feature issue closes only when every product surface is addressed or explicitly waived.
Written by the indexing model from the issue text.
Description
The founder, 2026-10-30: « quand tu dis c'est fait, c'est toutes les plateformes, CLI inclus ? » — today, no: « done » meant the issue's own scope. orazaka-cli only received pins and formatting this month while features moved on web/mobile/Mac (e.g. orazaka-cli#90 runs still open).
Make « done » cover every surface:
docs/standards/surfaces.json— per product, its surfaces: Orazaka = web client, web admin, mobile, Mac, CLI, API/SDK; Yomizaka = web, admin, mobile, Mac; Akinaza = web, admin, mobile, Mac.- Feature issue template: a « Surfaces » checklist generated from that file; each box ticked with its PR or marked
n/a — <reason>. - A check (org workflow) on closing a
featureissue: every surface ticked or justified, else the issue is reopened with a comment. Same check in the 30-min plan check. - Parity report per product (which features each surface lacks) in the weekly summary; CLI gaps become issues in the product's lane.
- Rolled out to every product repo (rules reach every repo).
🤖 Generated with Claude Code
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- Avg merge
- 2h 49m
- Merged PRs (30d)
- 212
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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 krizaka/.github
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
priority:P1 product:krizaka type:docs
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
public
Difficulty 4/5 3-5 days Newbie friendliness 25/100
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
krizaka/.github#427 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 18/100
krizaka/.github#423 · 1 comment ·
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
dbt-msft/dbt-sqlserver#897 ·
Maintainers usually reply within 1 day
-
area:docs area:stdlib found-by:duet-audit kind:docs-drift
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
InauguralSystems/EigenScript#2251 · 1 comment ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 1/5 1-3 hours Newbie friendliness 90/100
ivopogace/opencode-courier#422 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
beyondgrep/ack3#413 ·
-
Isaac workingOpen
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
seedds/nxnative#763 · 1 comment ·
Maintainers usually reply within 1 day