← all publishers

try-works

@try-works source repo

Report this profile Claim this profile

• 14 skills
• 0 followers
• 3 hours ago last updated

1. ▌
   Rlm Tdd · try-works bundle

   Use when implementing any code in RLM Phase 3. Enforces strict RED-GREEN-REFACTOR discipline with The Iron Law - no production code without a failing test first. Trigger phrases: "implement this", "add feature", "fix bug", "write a failing test", "TDD".
   0
   installs
2. ▌
   Rlm Subagent · try-works bundle

   Master skill for parallel subagent-driven execution with automatic fallback to single-agent sequential mode. Use when implementing plans with multiple independent sub-phases (SP1, SP2...) to dispatch parallel subagents, or when requiring code review between implementation and testing. Trigger phrases: "parallelize", "dispatch subagent", "split into sub-phases", "code review subagent", "parallel testing".
   0
   installs
3. ▌
   Rlm Debugging · try-works bundle

   Use when RLM requirement involves debugging a bug, test failure, or unexpected behavior. Insert Phase 1.5 between Phase 1 and Phase 2 to perform systematic root cause analysis before attempting any fixes. Trigger phrases: "debug", "investigate", "failing tests", "crash", "root cause".
   0
   installs
4. ▌
   Rlm Worktree · try-works bundle

   Use when starting any RLM requirement to set up an isolated git worktree. Required before Phase 1. Create an isolated workspace, verify the worktree directory is safe to use, run project setup, confirm a clean test baseline, and prevent direct main/master branch work.
   0
   installs
5. ▌
   Rlm Workflow Acp · try-works bundle

   Orchestrate the RLM repo workflow end to end with strict sequential phase gates, locked artifacts, traceability, TODO discipline, and optional ACP delegation to Kimi via `acpx`. Use for requests like "Implement requirement <run-id>", "Run RLM Phase <N>", "resume requirement", "lock Phase <N>", or "verify locks".
   0
   installs
6. ▌
   Recursive Tdd · try-works bundle

   Use when implementing any code in recursive-mode Phase 3. Enforces strict RED-GREEN-REFACTOR discipline with The Iron Law - no production code without a failing test first. Trigger phrases: "implement this", "add feature", "fix bug", "write a failing test", "TDD".
   0
   installs
7. ▌
   Recursive Mode · try-works bundle

   Repository workflow orchestration skill for staged implementation, locked artifacts, late-phase receipts, and durable memory maintenance. Use when executing recursive-mode runs, resuming a run, locking a phase, or verifying locks.
   0
   installs
8. ▌
   Recursive Spec · try-works bundle

   Approval-gated, repo-aware requirements/spec authoring for new recursive-mode runs. Use when the user wants help creating a plan, spec, scope, or requirements for work that does not yet have a run, especially prompts like "create a plan", "help me plan", "create a spec", "write requirements", or similar derivatives.
   0
   installs
9. ▌
   Recursive Router · try-works bundle

   Use when recursive-mode needs to route delegated audit, review, or bounded implementation work through external transports, CLIs, and models while preserving controller verification and fallback behavior.
   0
   installs
10. ▌
    Recursive Subagent · try-works bundle

    Use when recursive-mode work may benefit from delegated audit, review, or bounded implementation support. This skill prioritizes analyst, planner, code-reviewer, memory-auditor, tester, and implementer roles, with mandatory self-audit fallback when subagents are unavailable.
    0
    installs
11. ▌
    Recursive Training · try-works bundle

    Use after completed recursive-mode runs accumulate to extract durable experiential memory into `/.recursive/memory/`, then load it for later runs through the canonical loader.
    0
    installs
12. ▌
    Recursive Worktree · try-works bundle

    Use when starting any recursive-mode requirement to set up an isolated git worktree. Required before implementation phases: create an isolated workspace, verify a clean baseline, and keep main/master clean.
    0
    installs
13. ▌
    Recursive Debugging · try-works bundle

    Use when a recursive-mode requirement involves debugging a bug, test failure, or unexpected behavior. Insert Phase 1.5 between Phase 1 and Phase 2 to perform systematic root cause analysis before attempting any fixes. Trigger phrases: "debug", "investigate", "failing tests", "crash", "root cause".
    0
    installs
14. ▌
    Recursive Review Bundle · try-works bundle

    Use when recursive-mode work needs a canonical delegated-review or audit handoff. Generates reproducible review bundles for Phase 3.5 code review, test review, or other delegated checks using the repo review-bundle scripts.
    0
    installs