renanfranca
- 20 skills
- 0 followers
- 14 hours ago last updated
- ▌ Tdd Strict Cycle Confirmation · renanfranca bundleDrive strict test-driven development with explicit cycle boundaries and mandatory user confirmation after each completed cycle. Use when Codex should enforce red-green-refactor rigor while pausing at every cycle so the user can review code and approve continuation.
- ▌ Implement Approved Plan Deepseek · renanfranca bundleExecute an explicitly approved repository plan entirely inside DSH through an existing Coordinator session, six persistent top-level specialist sessions, serialized leases, behavioral TDD, independent validation, mutation testing, structural review, and GitHub delivery. Invoke as /implement-approved-plan-deepseek; never use to draft plans or merge pull requests.
- ▌ Tdd · renanfranca bundleGuide code changes with a strict test-driven development workflow using red-green-refactor, explicit failure prediction, and step-by-step confirmations at each TDD checkpoint. Use when Codex should drive or enforce TDD for new features, bug fixes, refactors, kata-style exercises, or collaborative implementation sessions where tests must lead the design and progress should be validated one small step at a time.
- ▌ Execplan Tdd · renanfranca bundleGuide repository code changes through a self contained living ExecPlan, behavior focused quiet TDD, a green public checkpoint, post GREEN design review, documentation reconciliation, and final validation. Use when Codex is asked to plan, implement, execute, or continue a software code change and the repository instructions declare a complete workflow profile. Do not use for skill development, documentation only changes, or repositories without the required profile.
- ▌ Specify Issue · renanfranca bundleCreate or revise a decision-complete normative software issue specification in .agent/specifications after repository research and focused user clarification. Use when the user asks to elaborate, specify, formalize, or refine an issue or requirements before implementation; do not use to implement the change or manage the resulting file in Git.
- ▌ Refactor Design · renanfranca bundleReview completed green implementations for structural design risks and apply behavior-preserving refactors with quiet output. Use after behavior-focused TDD or when a feature is functionally complete and Codex should inspect temporal coupling, hidden mutable state, mixed responsibilities, fragile representations, or architecture leakage before final validation. Do not use to discover new behavior or change public contracts.
- ▌ Create Git Branch · renanfranca bundleChoose and create safe, meaningful Git branches for repository-changing work. Use whenever Codex is asked to create, name, rename, suggest, select, or prepare a branch, and before implementation starts from the repository's default branch. Do not use for read-only work that does not need a branch.
- ▌ Commit The Changes · renanfranca bundleInspect repository commit history, infer the established commit message style and language, then stage and create a git commit that matches the repository convention. Use when the user asks to commit changes, asks for a commit message based on existing commits, or wants commits to follow the repository's established pattern.
- ▌ Implement Execplan · renanfranca bundleCreate, maintain, and execute self-contained ExecPlans for large, risky, cross-cutting, or handoff-sensitive repository work. Adapt plan structure and update cadence to the task; do not use for isolated mechanical edits unless explicitly invoked.
- ▌ Commit Staged Change · renanfranca bundleCreate Conventional Commits v1.0.0 messages and execute safe commits for already staged changes. Use when Codex should inspect history and staged diffs, align with repository conventions when they are already conventional, and run git commit safely.
- ▌ Seed4j Worktree Flow · renanfranca bundleManage the local seed4j-cli Git worktree workflow safely. Use when Codex is asked to audit seed4j-cli worktrees, create a feature worktree, clean up a completed worktree, decide which branches are already merged into main, or keep /home/renanfranca/projects/seed4j-cli as the main worktree while feature work happens under /home/renanfranca/projects/seed4j-cli-worktree.
- ▌ Switch Codex Account · renanfranca bundleManually switch Codex Desktop on Windows between two locally configured accounts, or inspect the switcher status. Use only when the user explicitly invokes $switch-codex-account for account-a, account-b, or status.
- ▌ Tdd Strict Autonomous · renanfranca bundleDrive strict test-driven development in autonomous mode using red-green-refactor without per-cycle user confirmations. Use when Codex should preserve TDD rigor for new features, bug fixes, refactors, or collaborative sessions while continuing automatically and pausing only on explicit exception gates.
- ▌ Implement Approved Plan · renanfranca bundleExecute a user-approved repository plan through serialized specialist Codex tasks, a guarded local ledger, independent validation, focal mutation testing, structural review, and pull-request/CI handoff. Invoke only when the user explicitly names $implement-approved-plan; do not use to draft plans, merge pull requests, or clean unmerged work.
- ▌ Seed4j CLI Model Runner · renanfranca bundleRun a controlled, auditable comparison of Codex models implementing one SPEC.md with Seed4J CLI. Use only when the user explicitly wants to create a public experiment repository, choose a model/reasoning-effort matrix, execute one new Codex task per result branch sequentially, and preserve each implementation and transcript for later evaluation.
- ▌ Restructure Documentation · renanfranca bundleAudit and restructure an existing repository documentation system around explicit audiences, user journeys, canonical sources, ordered concepts, and preserved public interfaces. Use for bloated README files, overlapping guides, concepts introduced out of order, duplicated normative facts, broken navigation, or requests to reorganize an existing set of documents. Do not use for isolated corrections, documentation written from scratch, style-only editing, or AGENTS.md changes unless the user explicitly requests a normative restructuring of those operational instructions.
- ▌ Seed4j CLI Model Evaluator · renanfranca bundleEvaluate frozen Seed4J CLI model experiment branches produced by seed4j-cli-model-runner. Use only when the user explicitly wants an evidence-linked technical comparison, README, MODEL_EVALUATION.md, Apache License 2.0, and a pull request to the specification-only main branch without changing any implementation branch.
- ▌ Tdd Strict Autonomous Quiet · renanfranca bundleDrive strict autonomous TDD with red-green-refactor while deliberately reducing message frequency, not merely message length. Use when tests must lead implementation, Codex should continue automatically, and user-facing output should appear only for essential risks, decisions, blockers, meaningful refactors, checkpoint failures, or the final compact summary.
- ▌ Approved Plan Title Bootstrap · renanfranca$implement-approved-plan bootstrap that gives the root task, Coordinator, and specialist tasks exact shared-prefix titles. Apply only when a message explicitly invokes $implement-approved-plan from its bootstrap task; do not use for an existing Coordinator or for unrelated title changes.
- ▌ Tdd Behavior Autonomous Quiet · renanfranca bundleDrive strict autonomous TDD with quiet output while ensuring tests follow observable behavior, public contracts, user journeys, or stable component APIs instead of production file/class structure. Use when tests must lead implementation, Codex should continue automatically, and new tests must avoid implementation-detail or one-test-per-file design.