samwelmunga
Community@samwelmunga
samwelmunga maintains the Jenga framework: 73 slash-command skills for scrum-board orchestration, git-integrated task execution, and project scaffolding.
Agent Skills by samwelmunga
Showing 72 vetted skills indexed across 2 GitHub repositories.
samwelmungaskill-name
Provides templates for authoring Jenga AI skills, board files, rapports, and permission levels.
samwelmungaj.status
Prints a human-readable summary of the scrum board, open rapports, and pending queue triggers.
samwelmungaj.help
Lists all available skills with descriptions as a slash-command table.
samwelmungaj.reconcile
Reconciles scrum board statuses against git history, worktrees, and actual code state.
samwelmungaj.deep-dive
Guides multi-phase investigation workflows through brainstorming, scrutiny review, and solution assessment.
samwelmungaj.dev-done
Chains commit and mirror-sync commands to sync framework changes into .claude/ and .agents/ mirrors.
samwelmungaj.dooo
Orchestrates parallel task execution by launching sub-agents and looping through eligible board items.
samwelmungaj.reconcile-origin
Rebase local commits onto the latest origin branch state with structured conflict reporting.
samwelmungaj.distribute
Distributes framework files from a monorepo to consuming projects with version bumping and dry-run preview.
samwelmungaj.doc
Generates complete Markdown documentation files from resolved path objectives and scrum-board evidence.
samwelmungaj.proceed
Reviews board progress and queues pending tasks for developer handoff.
samwelmungaj.jenga-permission-level
Report or switch the session's five-tier permission level via template-backed settings overwrites.
samwelmungaj.pi-plan
Defines and expands project Epics in PROJECT_SUMMARY.md for scrum-based planning.
samwelmungaj.jbp
Scaffolds a project using the JengaBasePlate boilerplate template from GitHub.
samwelmungaj.do
Executes scrum board tasks through developer agents with scope routing and rollback anchors.
samwelmungaj.idea
Captures loosely-defined ideas into a project ideas.md log without board overhead.
samwelmungaj.commit
Commits completed epic, story, or task work using the EST naming convention.
samwelmungaj.close-story
Closes scrum stories by verifying task states and writing git diff metrics to board frontmatter.
samwelmungaj.todo
Adds missions to a Markdown todo list linked to epics and stories.
samwelmungaj.playbook-new
Guides authoring of project-local playbook JSON files with catalog-validated inputs and post-write verification.
samwelmungaj.playbook
Invokes a named Jenga playbook by ID, skipping natural-language matching to run its skill chain.
samwelmungaj.wtf
Clarifies ambiguous or under-specified prompts via a collision-safe alias of the clearify skill.
samwelmungaj.dashboard-share
Snapshot the project dashboard and upload it to a configured rclone cloud remote.
samwelmungaj.btw
Captures new missions and files them into Epic and Story board structures.
Frequently Asked Questions About samwelmunga
FAQPage SchemaWhat tasks can I automate using samwelmunga's Jenga skills?▼
You can initialize structured projects, decompose epics into stories and tasks, execute board items with developer sub-agents, commit work under EST naming conventions, sync documentation with source code, scaffold ML training jobs, convert JSON/YAML datasets to CSV, and publish releases to npm, iOS, or droplet targets.
Who are the Jenga skills designed for?▼
They target developers and scrum-master personas working in agent-driven coding environments. Frontmatter metadata assigns preferred agents per skill: scrum-master for planning and board skills, developer for implementation and documentation, and tester for the guided error-troubleshooting flow.
How do the j-prefixed polyfill skills work at runtime?▼
Each j.* skill is a collision-safe alias identical to its bare slash-command counterpart, used when another tool's built-in command shadows the original name. For example, /j-status behaves exactly like /status, printing the full scrum board summary with open rapports and queue triggers.
What prerequisites and dependencies do the skills require?▼
Skills operate on a git repository with a standard Jenga directory structure including PROJECT_SUMMARY.md, workflow.json, project/todo.md, and .agents/skills folders. Dashboard sharing requires npm scripts in project/app plus rclone, which the j.cloud-connect wizard installs and configures.
How does Jenga handle releases and multi-project distribution?▼
The publish skill orchestrates staged releases to npm registries, iOS App Store, and droplet targets with dry-run previews and release notes. The distribute skill pushes framework files from the private monorepo to consuming projects with version bumping and post-distribution git commits.