Jake avatar

Jake

Community

@jakestrouse00 · United States of America

11Followers
|
41Public Repos
|
6Published Skills

22. Python, Javascript, HTML, CSS

Skills Distribution
DomainDeveloper To...Change Planning & .. (35%)Git Commit Managem.. (20%)Plan Backlog Maint.. (20%)Project Context Br.. (15%)

Agent Skills by Jake

Showing 6 vetted skills indexed across 1 GitHub repositories.

Frequently Asked Questions About Jake

FAQPage Schema
What tasks can I accomplish with jakestrouse00's opencode skills?

You can draft and create git commits, generate resumable step-by-step change outlines anchored to files and symbols, triage and archive completed plans, view an unfinished-plan dashboard, build project briefings for other agents, and discover available agents and skills.

Who are these skills designed for?

Developers using opencode in multi-project workspaces who lose track of in-progress changes, maintain plan backlogs under .opencode/plans/, or need structured context handoffs between agents. Familiarity with git and markdown-based plan files is assumed.

How do the plan and execution workflows operate?

change-outline writes a checklist to .opencode/plans/<slug>.md and hard-stops; execution only begins when the user literally says 'execute <slug>'. Completed plans are auto-marked Status: complete and moved to .opencode/plans/archive/, enabling cross-session resume.

Are these skills safe to run on my repository?

Yes, with clear boundaries. Read-only skills (help-me, plan-dashboard, project-briefing) never edit anything. Mutating skills are constrained: commit-code never pushes, amends, or force-pushes; plan-triage never executes plans, touches source code, deletes, or commits.

What prerequisites do these skills require?

An opencode environment with agents under .opencode/agent/ and skills under .opencode/skills/, plus a git working tree for commit-code. Plan features rely on markdown plan files stored in .opencode/plans/ with an archive/ subdirectory.