martin-francois/symphony-trello
Skill Claude CodeCodex
Safe-by-default Symphony for Trello bug bash. Uses fake Trello, fake Codex, and fake/local GitHub unless explicitly asked for a real live bug bash; the phrase "hardened host" enables run-scoped danger-full-access and Codex dangerous-bypass coverage. Covers SPEC.md conformance, installers, CLI options, workflow…
martin-francois/symphony-trello
Skill Claude CodeCodex
Explicit-only publisher for reviewed live-bugbash issue drafts. Creates new GitHub issues for unique confirmed findings and comments on duplicate issues with sanitized reproduction details. Never runs the bug bash.
martin-francois/symphony-trello
Skill Claude CodeCodex
Create a focused commit from the current staged changes. Use when asked to commit, prepare a commit, or finalize a Symphony-for-Trello issue branch.
martin-francois/symphony-trello
Skill Claude CodeCodex
Diagnose stuck, retrying, blocked, or failed Symphony-for-Trello runs. Use when a card is not moving, a worker is retrying, comments show blockers, or a deployment smoke test fails.
martin-francois/symphony-trello
Skill Claude CodeCodex
Create or synchronize Trello cards from GitHub issues for Symphony for Trello. Use when the user asks Codex to create Trello cards from specific GitHub issue URLs, issue numbers, or issue lists, optionally for a specific Trello board, or when a board should be auto-selected from a workflow whose repository…
martin-francois/symphony-trello
Skill Claude CodeCodex
Run a repository-wide GitHub issue triage sweep for Symphony for Trello. Use when the user asks for an issue sweep, issue triage audit, issue audit, cleanup of issue labels, or to check open issues for stale scope, dependencies, already-implemented work, labels, milestones, or template quality.
martin-francois/symphony-trello
Skill Claude CodeCodex
Use in Symphony for Trello when a Java change or review presents a reusable Optional or absence/fallback strategy-selection lesson, including on an adjacent owning API such as ScopedValue even when no java.util.Optional appears. Capture the before/prompt/after code and create or update a self-contained eval issue in…
martin-francois/symphony-trello
Skill Claude CodeCodex
Use in Symphony for Trello when a Java change or review presents a reusable lesson about choosing or preserving a stream, collector, direct result-producing collection transformation, or character-predicate traversal, including identity or delimited string reductions, even when the preferred final code contains no…
martin-francois/symphony-trello
Skill Claude CodeCodex
Merge an approved pull request after a Trello card has been moved to Merging. Use only for human-approved work where the workflow explicitly allows merging from Merging.
martin-francois/symphony-trello
Skill Claude CodeCodex
Push a branch and create or update the matching GitHub pull request. Use when publishing work, updating a PR, or preparing a branch for human review.
martin-francois/symphony-trello
Skill Claude CodeCodex
Sync a feature branch with the default branch and resolve conflicts. Use when the branch is stale, a push is rejected, CI needs the latest main, or merging needs a conflict-free branch.
martin-francois/symphony-trello
Skill Claude CodeCodex
Gather and resolve pull request feedback before Trello handoff or merging. Use when a Trello card links to a PR, a branch has a PR, or work is being moved to Human Review or Merging.
martin-francois/symphony-trello
Skill Claude CodeCodex
Move the current Trello card through the configured Symphony-for-Trello lifecycle. Use when picking up work, handing off for human review, marking a blocker, or completing a merge.
martin-francois/symphony-trello
Skill Claude CodeCodex
Maintain the single Codex workpad comment on the current Trello card. Use during implementation, retry, rework, review handoff, blocked handoff, or merge handoff.
martin-francois/symphony-trello
Instructions file CodexOpenCode
AGENTS.md instructions for martin-francois/symphony-trello, covering agent operating instructions, maintenance, more detailed instructions (progressive disclosure) and agent rules.
martin-francois/symphony-trello
Instructions file
Claude Code instructions for martin-francois/symphony-trello, a project described as: Turn Trello cards into isolated, autonomous Codex implementation runs, allowing teams to manage work instead of supervising coding agents.
martin-francois/symphony-trello
Agent
How much to decide independently, when to ask the user, and how to run the Codex review/fix loop on this repository.
martin-francois/symphony-trello
Agent
The order of work for any task: what to read first, how to scope a change, how to verify, and how to commit and open pull requests. Topic-specific rules live in the pages linked under References.
martin-francois/symphony-trello
Agent
This page defines dependency declaration, Renovate ownership, release-age, and automatic-merge requirements.
martin-francois/symphony-trello
Agent
How to deploy and verify Symphony for Trello against real systems: when to run live deployment verification, how live end-to-end runs must be structured, deployment auth and filesystem access, shipped-skill installation, and installer/onboarding lifecycle coverage. Unit/integration testing lives in Testing.
martin-francois/symphony-trello
Agent
How to run issue triage sweeps, manage issue dependencies, and apply triage labels. Spec-alignment auditing that may create issues lives in Specification & ADR discipline.
martin-francois/symphony-trello
Agent
How to write and shape Java code in this repository: formatting, language-feature use, complexity and reuse tradeoffs, and exception handling. Static-analysis tooling has its own page; see References.
martin-francois/symphony-trello
Agent
Agent "maintaining-agent-docs" from martin-francois/symphony-trello, covering maintaining agent docs, progressive disclosure contract, what may be added to agents.md (allowlist), what must not be added to agents.md (denylist) and where to put new guidance (decision tree).
martin-francois/symphony-trello
Agent
How to keep private project internals out of committed files, GitHub issues, and user-facing summaries, and how to use the local diagnostics tooling for private investigation.