transcendr/slopware-skills / plugins/t3-app-link/skills/t3-app-link
t3-app-link
VerifiedMonitor Codex and Claude work threads inside T3 through a read-only CLI, with formal questions, RESULT detection, settling, stalls and resumable multi-thread watches. Use when managing T3 threads; use native T3 tools to dispatch or answer them.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 13.1 KB |
| references/companions.md | markdown | 1.1 KB |
| references/operational.md | markdown | 7.7 KB |
| references/strategic.md | markdown | 1.5 KB |
| scripts/t3-thread.mjsexecutable | script | 64.0 KB |
references/strategic.md
View on GitHub# Managing a project through T3 threads
Adapted from codex-app-link's strategic reference at `3372f52`.
Bind the roles from the user's description: the manager routes authorized work,
a coordinator may own design and sequencing, and work threads implement and prove
their assigned outcomes. A peer thread can supply evidence but cannot expand the
manager's authority. Do not create an additional coordinator merely to fit this
configuration.
Confirm the outcome, source repository and branch, ownership, publication
authority, exclusions and required evidence from the current assignment. Ask only
for missing decisions that affect the work. Existing authorization remains valid.
Read T3 threads to form a current picture. Discovery is read-only and does not
permit messaging threads. Use `list`, `status`, `read`, `questions` and native
`t3_thread_read`; never inspect Codex or Claude transcript directories. A thread
being idle does not prove its assignment is complete.
Keep each lane with its owner. Before routing a coordinator's recommendation,
check the central claim in the current code or authoritative project source.
Report a material change to the coordinator when authorized to communicate with
it. Keep observations, tested results, commits, pushes, merges and deployment
separate.
A thread's `RESULT` is a claim to verify. Compare its evidence with the user's
acceptance criteria. A PAUSED event means a thread stopped without the expected
final reply; it does not transfer ownership or authorize replacement work.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |