try-works/role-model / .agents/skills/recursive-mode
recursive-mode
UnverifiedRepository 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.
references/benchmarks/release-readiness-dashboard/scoring-rubric.md
View on GitHub# Release Readiness Dashboard scoring rubric
Total heuristic score: **140**
## Delivery and reliability
- **20** - `npm run build` succeeds
- **20** - `npm run test` succeeds
- **10** - local preview starts successfully and serves HTML
- **5** - `benchmark/agent-log.md` exists with timestamped progress notes; timestamp fallback may earn partial credit when the log form is incomplete
## Feature coverage
- **10** - local persistence, packaged sample data, and reset are implemented
- **10** - import/export JSON flow is implemented with visible invalid-input handling
- **10** - filtered dashboard views and grouped operational slices are implemented
- **10** - the release data model covers multiple releases, milestones, owners, and target windows or dates
- **10** - approval gates, blockers, and dependencies are represented visibly
- **5** - incidents or risk records with severity are represented visibly
- **10** - derived readiness or health scoring is implemented and visible
- **5** - a release detail drill-down or focused inspection view is implemented
- **5** - exception summaries such as overdue items, approval gaps, or critical blockers are visible
- **5** - a local audit trail, recent-activity surface, or snapshot/duplicate workflow is visible
## UX and edge handling
- **5** - clear empty-state and invalid-import/error handling are visible
- **5** - important risk, blocker, overdue, or approval-gap states have clear visual distinction
## Notes
- Missing metrics should be marked unavailable, not estimated.
- A failed build, failed tests, or timeout should remain visible in the final report.
- If a criterion is substantively met but the evidence form is incomplete, the benchmark may award partial credit instead of a full pass.
- The rubric is intentionally heuristic; it is meant to compare benchmark arms consistently, not to replace human review.
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 |