Skip to content

docs: add task breakdown for issue #39 - #40

Merged
rsenna merged 3 commits into
mainfrom
issue-39-task-breakdown
Aug 1, 2026
Merged

docs: add task breakdown for issue #39#40
rsenna merged 3 commits into
mainfrom
issue-39-task-breakdown

Conversation

@owkwo-bot

@owkwo-bot owkwo-bot commented Aug 1, 2026

Copy link
Copy Markdown
Collaborator

Summary

Task breakdown for #39 (chore: adopt repo-standard, stage=in-progress), per map-issue-to-tasks. Doc/planning only, no source changes.

4 tasks: declare stage in repo.toml, create AGENTS.md, create empty specs//specs/decisions/, bootstrap .specify/ from the iklo reference implementation (the last one needs authoring guiltty's own constitution content, not a copy). Enrichment already posted as an issue comment on #39; issue labeled mapped.

Test plan

  • Follows the same Acceptance/Verify/Files/Dependencies shape as tasks/issue-16-*.md and tasks/issue-8-*.md
  • pr-review-toolkit:review-pr pass in progress

🧙 Built with WOZCODE

Summary by Sourcery

Documentation:

  • Add tasks/issue-39-*.md planning document outlining acceptance, verification, files, and dependencies for adopting the repo-standard and scaffolding related documentation and tooling.

Summary by cubic

Adds a task breakdown for issue #39 to adopt the repo standard and move the repo to the in-progress stage. Planning-only docs; no source or CI changes, and fixes section reference plus verification, linking, and copy-command details in the task doc.

Written for commit 1686a6b. Summary will update on new commits.

Review in cubic

Summary by CodeRabbit

  • Documentation

    • Added a detailed task plan for adopting the repository’s standard “in-progress” stage.
    • Documented planned updates for repository conventions, structure, commands, specifications, decision records, governance, and verification.
  • Chores

    • Defined sequencing, dependencies, acceptance criteria, and verification steps for metadata and repository scaffolding.
    • Clarified non-goals: no application behavior, Rust code, CI workflows, or existing documentation were changed.

Written during map-issue-to-tasks but not yet committed.

Co-Authored-By: WOZCODE <contact@withwoz.com>
@gemini-code-assist

Copy link
Copy Markdown

Caution

The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased.

@sourcery-ai

sourcery-ai Bot commented Aug 1, 2026

Copy link
Copy Markdown

Reviewer's Guide

Adds a new task breakdown document for issue #39 that defines four documentation-only tasks to adopt the cross-repo standard and reach the "in-progress" stage, including repo.toml stage declaration, AGENTS.md creation, specs/ scaffolding, and .specify/ bootstrap from the iklo reference implementation.

Flow diagram for task sequencing in issue 39 repo-standard adoption

flowchart TD
  Start[Begin issue 39] --> T1
  Start --> T3

  T1[Declare stage in repo.toml] --> T2
  T3[Create specs/ and specs_decisions directories] --> T4
  T2[Create AGENTS.md] --> T4

  T4[Bootstrap .specify from iklo reference] --> Done[Issue 39 tasks complete]
Loading

File-Level Changes

Change Details Files
Introduce a task breakdown doc for issue #39 that follows the existing tasks template conventions.
  • Create a new tasks markdown file for issue chore: adopt repo-standard (stage=in-progress) #39 using the same Acceptance/Verify/Files/Dependencies structure as prior issue task docs.
  • Document that the issue is scaffolding-only with no Rust source, docs relocation, or CI changes.
  • Describe sequencing relationships among the four tasks (T1–T4) to guide implementation order.
tasks/issue-39-chore-adopt-repo-standard-stage-in-progress.md
Define task T1 to declare the repository stage in repo.toml.
  • Specify adding a single stage = "in-progress" line to repo.toml matching the design doc values.
  • State that no other repo.toml fields should be modified.
  • Describe verification via inspecting repo.toml for only the new line in the diff.
tasks/issue-39-chore-adopt-repo-standard-stage-in-progress.md
Define task T2 to create an AGENTS.md hub document at the repo root.
  • Outline the required content for AGENTS.md in terms of implemented status, rules/conventions, dev commands, and project structure mapping.
  • Require that AGENTS.md mirrors and links existing spec and design docs instead of duplicating their content.
  • Specify verification by cross-checking AGENTS.md claims against docs/spec.md and the current crate tree to ensure they reflect reality.
tasks/issue-39-chore-adopt-repo-standard-stage-in-progress.md
Define task T3 to scaffold specs/ and specs/decisions/ directories with .gitkeep files.
  • Require creating specs/ and specs/decisions/ directories each containing a .gitkeep to make empty dirs trackable.
  • Explicitly state that no existing docs/spec*.md or docs/design/*.md files should be moved into these directories.
  • Describe verification via git status to confirm only empty directories with .gitkeep are added.
tasks/issue-39-chore-adopt-repo-standard-stage-in-progress.md
Define task T4 to bootstrap the .specify/ tree from the iklo reference implementation and author a guiltty-specific constitution.
  • Specify copying project-agnostic subtrees (templates, scripts/bash, workflows, integrations) verbatim from iklo's .specify/ layout.
  • Require authoring .specify/memory/constitution.md specifically for guiltty by translating existing code style and architectural rules into constitutional articles, without reusing iklo-specific content.
  • Call out the need to review .specify/scripts/bash/*.sh for extra tool dependencies and either add them to mise.toml or document follow-ups, plus verification via directory diff and constitution content review.
tasks/issue-39-chore-adopt-repo-standard-stage-in-progress.md

Possibly linked issues


Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@greptile-apps greptile-apps Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

owkwo-bot has reached the 50-credit limit for trial accounts. To continue receiving code reviews, upgrade your plan.

@coderabbitai

coderabbitai Bot commented Aug 1, 2026

Copy link
Copy Markdown

Review Change Stack

📝 Walkthrough

Walkthrough

The pull request adds a task plan for adopting the repository’s in-progress standard. It defines work for stage metadata, repository guidance, specification directories, .specify/ tooling, a constitution, dependency checks, verification, sequencing, and non-goals.

Changes

Repository standard adoption

Layer / File(s) Summary
Stage, guidance, and specification scaffolding
tasks/issue-39-chore-adopt-repo-standard-stage-in-progress.md
Defines tasks to declare stage = "in-progress", create root AGENTS.md, add tracked .gitkeep files under specs/ and specs/decisions/, and verify the planned changes.
.specify tooling and constitution
tasks/issue-39-chore-adopt-repo-standard-stage-in-progress.md
Defines tasks to copy project-agnostic tooling, author a guiltty-specific constitution, inspect script dependencies, and verify the result.

Estimated code review effort: 1 (Trivial) | ~3 minutes

Possibly related issues

  • rsenna/obsidian-hivemind#30 — Defines the same repository-standard adoption tasks.
  • rsenna/guiltty#39 — Directly describes the planned in-progress adoption work.
  • rsenna/what-about#58 — Covers the same stage, directory, and .specify/ tasks.
  • rsenna/iklo#46 — Shares the in-progress stage adoption and related artifact work.
  • rsenna/roset.sh#8 — Shares the repo.toml stage declaration and related scaffolding.
🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and concisely describes the documentation-only task breakdown added for issue #39.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch issue-39-task-breakdown

Comment @coderabbitai help to get the list of available commands.

@codacy-production

Copy link
Copy Markdown

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

AI Reviewer: first review requested successfully. AI can make mistakes. Always validate suggestions.

Run reviewer

TIP This summary will be updated as you push new changes.

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey - I've found 1 issue, and left some high level feedback:

  • The references to ~/REPO/ME/iklo/.specify/ and local paths assume a specific local checkout layout; consider rephrasing these instructions in terms of repo-relative paths or a cloned reference repo so they’re easier for other contributors to follow.
  • The verification steps that rely on diff -rq and other shell tooling are a bit environment-specific; you might want to spell out an equivalent, more platform-agnostic check or at least note the assumptions (GNU diff, bash, etc.).
  • For T4’s handling of additional tool dependencies (like jq), it may be clearer to separate the possible follow-up into a distinct task or explicit checklist item so it’s tracked consistently rather than just mentioned inline.
Prompt for AI Agents
Please address the comments from this code review:

## Overall Comments
- The references to `~/REPO/ME/iklo/.specify/` and local paths assume a specific local checkout layout; consider rephrasing these instructions in terms of repo-relative paths or a cloned reference repo so they’re easier for other contributors to follow.
- The verification steps that rely on `diff -rq` and other shell tooling are a bit environment-specific; you might want to spell out an equivalent, more platform-agnostic check or at least note the assumptions (GNU diff, bash, etc.).
- For T4’s handling of additional tool dependencies (like `jq`), it may be clearer to separate the possible follow-up into a distinct task or explicit checklist item so it’s tracked consistently rather than just mentioned inline.

## Individual Comments

### Comment 1
<location path="tasks/issue-39-chore-adopt-repo-standard-stage-in-progress.md" line_range="104" />
<code_context>
+  public API"), in the same spirit as iklo's constitution (principles that
+  govern every spec/plan/task, amendments via an ADR under
+  `specs/decisions/`) but with guiltty's own content, not iklo's.
+- Before treating this done, skim `.specify/scripts/bash/*.sh` for any tool
+  dependency (e.g. `jq`) not already covered by `mise.toml`; if one exists,
+  either add it to `mise.toml` as part of this task or note it explicitly as
</code_context>
<issue_to_address>
**nitpick (typo):** Minor grammar tweak: "Before treating this as done" reads more naturally.

The phrase is missing "as"; please update it to either "Before treating this as done" or "Before considering this done" for correct grammar and clearer readability.

```suggestion
- Before treating this as done, skim `.specify/scripts/bash/*.sh` for any tool
```
</issue_to_address>

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

Comment thread tasks/issue-39-chore-adopt-repo-standard-stage-in-progress.md Outdated

@codacy-production codacy-production Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR provides a comprehensive task breakdown (T1-T4) to bring the repository into compliance with the 'in-progress' stage of the repository standard. The document correctly incorporates requirements for metadata updates, documentation hubs, and directory scaffolding.

While the document follows the required formatting and addresses all acceptance criteria, a reproducibility issue was identified in Task T4. Specifically, the inclusion of local absolute file paths in the verification steps will prevent other team members from executing the tasks as written. Addressing this will ensure the documentation is actionable across the team.

Test suggestions

  • Verify the task document follows the established format (Acceptance/Verify/Files/Dependencies sections per task).
  • Verify T1 specifies the 'in-progress' stage as one of the four valid values (prototype | in-progress | released | archived).
  • Verify T4 explicitly requires authoring original constitution content rather than copying from the reference implementation.

TIP Improve review quality by adding custom instructions
TIP How was this review? Give us feedback

Comment thread tasks/issue-39-chore-adopt-repo-standard-stage-in-progress.md Outdated

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 5

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@tasks/issue-39-chore-adopt-repo-standard-stage-in-progress.md`:
- Around line 110-114: Update the T4 verification command to iterate over
templates, scripts, workflows, and integrations individually, comparing each
source subdirectory under the iklo repository with its matching .specify
subdirectory via diff -rq.
- Around line 52-55: Replace the wildcard docs/design/*.md reference in the
AGENTS.md guidance with concrete Markdown links to each existing design
document, or link to a stable design index page. Ensure every link resolves to
an actual document and preserve the hub-page approach without duplicating
document content.
- Around line 30-32: Update the verification instructions to use Git-based
checks: inspect the diff for repo.toml to confirm only the intended line
changed, verify both directories explicitly, and check both tracked .gitkeep
paths individually rather than relying on git status directory output.
- Around line 57-60: Expand the AGENTS.md verification step beyond
crates/*/src/lib.rs to inspect workspace manifests, all crate source files,
examples, tests, and referenced documentation, while also checking README
status, commands, workspace layout, and links against docs/spec.md and the
current repository tree. Ensure every “implemented” claim matches the actual
repository contents.
- Around line 13-19: Update the T4 sequencing and file-scope details in the task
document to declare its dependency on T3, since T3 creates specs/decisions/
required by T4’s ADR guidance. Add mise.toml as a conditional T4 output for
tool-audit changes, or specify an owned follow-up if it remains out of scope,
and apply these corrections consistently to the other referenced T4 sections.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 54da9d39-4600-49d8-82de-a34070ee39ae

📥 Commits

Reviewing files that changed from the base of the PR and between cec3425 and c9c45fc.

📒 Files selected for processing (1)
  • tasks/issue-39-chore-adopt-repo-standard-stage-in-progress.md

Comment thread tasks/issue-39-chore-adopt-repo-standard-stage-in-progress.md Outdated
Comment thread tasks/issue-39-chore-adopt-repo-standard-stage-in-progress.md Outdated
Comment thread tasks/issue-39-chore-adopt-repo-standard-stage-in-progress.md
Comment thread tasks/issue-39-chore-adopt-repo-standard-stage-in-progress.md Outdated
Comment thread tasks/issue-39-chore-adopt-repo-standard-stage-in-progress.md
The Always/Ask first/Never list is docs/spec.md's Boundaries section,
not Code Style -- caught by pr-review-toolkit:review-pr.

Co-Authored-By: WOZCODE <contact@withwoz.com>

@cubic-dev-ai cubic-dev-ai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

4 issues found and verified against the latest diff

Confidence score: 4/5

  • In tasks/issue-39-chore-adopt-repo-standard-stage-in-progress.md, the T4 diff -rq example uses brace expansion that produces too many operands, so contributors can’t run verification as written and may get false confidence from a broken check — rewrite it as explicit pairwise comparisons or a loop that calls diff with exactly two paths each time.
  • In tasks/issue-39-chore-adopt-repo-standard-stage-in-progress.md, the verification criteria depend on ~/REPO/ME/iklo/.specify/, which is machine-specific and makes the task non-reproducible for others — switch to repo-relative paths or a documented environment variable.
  • In tasks/issue-39-chore-adopt-repo-standard-stage-in-progress.md, T4 is marked dependency-free even though it references artifacts created in T3 (specs/decisions/) and may touch mise.toml, creating ordering and scope ambiguity — declare T3 as a prerequisite and include mise.toml in T4 outputs if it can change.
  • In tasks/issue-39-chore-adopt-repo-standard-stage-in-progress.md, verification only checking crates/*/src/lib.rs under-validates AGENTS.md claims, so documentation and workspace drift can slip through undetected — expand checks to manifests, broader crate sources, and referenced docs/links.
Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="tasks/issue-39-chore-adopt-repo-standard-stage-in-progress.md">

<violation number="1" location="tasks/issue-39-chore-adopt-repo-standard-stage-in-progress.md:59">
P3: Checking only `crates/*/src/lib.rs` isn't enough to verify all of `AGENTS.md`'s claims (README status, dev commands, workspace layout, and links). Broaden verification to include the workspace manifests, all crate source files/examples/tests, and the referenced docs.</violation>

<violation number="2" location="tasks/issue-39-chore-adopt-repo-standard-stage-in-progress.md:111">
P2: The T4 verify command can't run as written. Shell brace expansion turns `{templates,scripts,workflows,integrations}` into four separate path arguments, but `diff -rq` only supports comparing two operands, so this invocation errors out with 'extra operand' instead of checking that the copied project-agnostic `.specify/` directories match iklo's. Since this step exists specifically to gate acceptance, an executor following it verbatim can't complete the check. Consider splitting it into per-directory diffs.</violation>

<violation number="3" location="tasks/issue-39-chore-adopt-repo-standard-stage-in-progress.md:111">
P2: The verification criteria hard-code a local absolute path (`~/REPO/ME/iklo/.specify/`), which won't resolve on another contributor's machine and makes this task non-reproducible. Use a portable reference such as a relative workspace path or repository URL instead.</violation>

<violation number="4" location="tasks/issue-39-chore-adopt-repo-standard-stage-in-progress.md:118">
P2: T4 is listed as having no dependencies, but its constitution content points amendment ADRs to `specs/decisions/`, which is only created by T3, and its tool audit step can modify `mise.toml`, which isn't listed under `Files`. Consider marking T3 as a soft dependency and listing `mise.toml` as a conditional output.</violation>
</file>

Reply with feedback, questions, or to request a fix.

Re-trigger cubic

Comment thread tasks/issue-39-chore-adopt-repo-standard-stage-in-progress.md Outdated
Comment thread tasks/issue-39-chore-adopt-repo-standard-stage-in-progress.md Outdated
Comment thread tasks/issue-39-chore-adopt-repo-standard-stage-in-progress.md Outdated
Comment thread tasks/issue-39-chore-adopt-repo-standard-stage-in-progress.md Outdated
- T1 Verify: cat repo.toml didn't prove nothing else changed; use
  git diff repo.toml instead.
- T2: docs/design/*.md doesn't resolve as a real Markdown link; list
  the three actual files. Broaden T2's Verify beyond crates/*/src/lib.rs
  since AGENTS.md will also claim things about dev commands, workspace
  layout, and doc links that lib.rs alone can't confirm.
- T3 Verify: git tracks files, not empty directories; reworded to what
  git status actually shows (the two .gitkeep files).
- T4: the diff -rq command with brace expansion passes four source
  operands plus one dest operand, which diff can't accept -- replaced
  with a per-directory loop. Softened the hardcoded ~/REPO/ME/iklo path
  reference (maintainer's own layout; clone rsenna/iklo temporarily
  otherwise). Declared T3 as T4's soft dependency (constitution content
  references specs/decisions/, which T3 creates) and added mise.toml as
  a conditional Files entry. Fixed a small typo.

Independently re-verified via pr-review-toolkit:review-pr before
pushing -- all fixes confirmed correct, one dash-style nit also fixed.

Co-Authored-By: WOZCODE <contact@withwoz.com>
@owkwo-bot

Copy link
Copy Markdown
Collaborator Author
  • The references to ~/REPO/ME/iklo/.specify/ and local paths assume a specific local checkout layout; consider rephrasing these instructions in terms of repo-relative paths or a cloned reference repo so they're easier for other contributors to follow.
  • The verification steps that rely on diff -rq and other shell tooling are a bit environment-specific; you might want to spell out an equivalent, more platform-agnostic check or at least note the assumptions (GNU diff, bash, etc.).
  • For T4's handling of additional tool dependencies (like jq), it may be clearer to separate the possible follow-up into a distinct task or explicit checklist item so it's tracked consistently rather than just mentioned inline.

First two fixed in 1686a6b: noted the ~/REPO/ME/iklo path is the maintainer's own dev-machine layout (matching the issue's own wording) with "clone rsenna/iklo temporarily" as the portable alternative, and fixed the diff -rq command itself (it was actually broken -- brace expansion made it pass 4 source operands plus 1 dest operand, which diff can't accept -- now a per-directory loop). Not spelling out a GNU-diff-specific caveat beyond that; this is a planning doc, not a script that needs to run on arbitrary platforms.

Third one: left as an inline note rather than a separate task/checklist item -- it's a small, conditional "check while you're in there" step (skim the vendored scripts for an undeclared tool dependency), not substantial enough on its own to warrant its own T5. If T4's implementer does find something, mise.toml is now listed as a conditional Files entry for T4 itself to capture that.

@rsenna
rsenna merged commit 8cc5e85 into main Aug 1, 2026
4 checks passed
@rsenna
rsenna deleted the issue-39-task-breakdown branch August 1, 2026 14:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants