daily-working

A Claude Code plugin/skill that coordinates a full task-to-verified-change loop:

1. Fetch the task/ticket from Redmine by ID, including attachments (screenshots, mockups, logs) that often carry the actual requirement — and check the ticket isn't already claimed or closed.
2. Implement the change with the Claude CLI, following the target project's existing conventions — on a dedicated branch, marking the ticket "in progress" first.
3. Verify the change in a real running UI via the claude-in-chrome extension.
4. Close the loop: open a PR with a proper summary/test/verification body, then move the ticket to "in review" on Redmine once the browser check is confirmed — final Resolved/Closed happens separately, after the PR actually merges.

If the requirement is ambiguous, the skill asks in-chat first and, if that doesn't resolve it, escalates by posting the question as a Redmine comment and pausing — the reporter/PM watches the ticket, not this conversation.

See skills/daily-working/SKILL.md for the full workflow this skill runs.

Architecture

End-to-end pipeline across four phases, plus a one-time setup phase that adapts the skill to whatever repo it's running in:

flowchart TD
    P0["Phase 0 — Project Setup (first run only)<br/>Read target repo's CLAUDE.md / CONTRIBUTING / README<br/>Ask short questionnaire for what's still unclear<br/>Save .claude/daily-working.yml"] --> P1

    P1["Phase 1 — Fetch Task<br/>Pull ticket + attachments from Redmine<br/>(browser session or API key)<br/>Check it isn't already claimed/closed"] --> AMBIG{Requirement clear?}

    AMBIG -- "No" --> ESC["Ask in-chat, then escalate<br/>as a Redmine comment and pause"]
    ESC -.-> P1
    AMBIG -- "Yes" --> P2

    P2["Phase 2 — Implement<br/>Branch + code changes via Claude CLI,<br/>following the project's own conventions<br/>Mark ticket 'In Progress'"] --> P3

    P3["Phase 3 — Verify<br/>Drive the real running UI<br/>via the claude-in-chrome extension"] --> P4

    P4["Phase 4 — Close the Loop<br/>Open PR with summary/test/verification<br/>Move ticket to 'In Review'<br/>(Resolved/Closed happens later, after merge)"]

Quick Start

# 1. Clone
git clone https://github.com/tms-tungnguyen3/daily_working.git
cd daily_working

# 2. Install (as a Claude Code plugin)
/plugin marketplace add tms-tungnguyen3/daily_working
/plugin install daily-working@daily-working-marketplace

# 3. Run — from any target project, just hand Claude Code a ticket ID
"Pull Redmine ticket #4626 and implement it"

First time in a given repo, the skill runs a short Phase 0 setup (see below) before doing any work. Every run after that reuses the saved config.

Use Cases

• You get work as Redmine tickets and want the whole cycle automated — fetch, implement, verify, open PR, and update ticket status — instead of manually copy-pasting the ticket description into chat and flipping Redmine status by hand.
• You don't trust "tests pass" as proof a change actually works — Phase 3 drives the real running app in a browser via claude-in-chrome before a PR ever opens.
• Requirements are sometimes ambiguous and the reporter/PM isn't in this chat — the skill escalates the question onto the ticket itself (a Redmine comment) instead of guessing or stalling silently.
• You work across several repos with different conventions — Phase 0 reads each target repo's own CLAUDE.md/CONTRIBUTING.md/README.md first, then asks only for what's still unclear, and saves it per-repo so it's never re-asked.

Install

As a plugin (recommended once published):

/plugin marketplace add <owner>/<repo>
/plugin install daily-working@daily-working-marketplace

(Replace <owner>/<repo> with wherever this repo ends up hosted, e.g. on GitHub, once pushed.)

As a personal skill (available in every project, no plugin needed):

mkdir -p ~/.claude/skills/daily-working
cp skills/daily-working/SKILL.md ~/.claude/skills/daily-working/SKILL.md

As a project skill (checked into one specific repo, shared with anyone using it):

mkdir -p <target-project>/.claude/skills/daily-working
cp skills/daily-working/SKILL.md <target-project>/.claude/skills/daily-working/SKILL.md

First run in a project

The skill is generic by design — it doesn't hardcode any one project's ticket-key format, architecture, test command, or PR flow. The first time it runs in a repo, it asks a short setup questionnaire (Redmine URL, ticket key prefix, your Redmine username, commit format, branch naming, conventions, test command, whether the dev DB is shared, how to signal work has started/is in review on a ticket, PR method, dev server URL) and saves the answers to .claude/daily-working.yml at that git repo's root — not in this plugin repo. Every later run reads that file instead of asking again. It's safe to commit (conventions only, no credentials) so a team shares one setup.

If you work out of a parent folder that holds several independent repos (a monorepo-style layout where the parent itself isn't a git repo), each repo gets its own .claude/daily-working.yml rather than one shared at the parent — conventions and test commands are usually not interchangeable across repos even when they live under the same folder.

Uninstall

If installed as a plugin:

/plugin uninstall daily-working@daily-working-marketplace

This removes the plugin but keeps the marketplace registered (so you can reinstall later). To also drop the marketplace itself:

/plugin marketplace remove daily-working-marketplace

Removing the marketplace uninstalls any plugin installed from it, so you don't need to run both — marketplace remove alone is enough if you're done with it entirely.

Prefer disabling over uninstalling if you just want it out of the way temporarily: /plugin disable daily-working@daily-working-marketplace (re-enable later with /plugin enable ..., no reinstall needed).

If installed as a personal skill (~/.claude/skills/):

rm -rf ~/.claude/skills/daily-working

If installed as a project skill (<project>/.claude/skills/):

rm -rf <target-project>/.claude/skills/daily-working

Either way, also remove the per-project config it generated in Phase 0, if you no longer want it:

rm <target-project>/.claude/daily-working.yml   # or .json

That file is independent of how the skill itself was installed — deleting the skill doesn't remove it, and vice versa.

Requirements

• The claude-in-chrome browser extension, for Phase 1 (optional) and Phase 3 (verification).
• A Redmine instance with either an authenticated browser session or an API key (REDMINE_URL / REDMINE_API_KEY).
• Project-specific conventions (test framework, DB safety rules, commit format) are assumed to already exist in the target codebase — this skill coordinates around them, it doesn't define them.

License

MIT — see LICENSE.