Classify new project missions into existing Epic and Story hierarchies.
npx skills add https://github.com/samwelmunga/JengaAgent --skill btw-samwelmunga
Please help me install this Agent Skill. Skill: btw Source: https://github.com/samwelmunga/JengaAgent/tree/main/.agents/skills/btw Command: npx skills add https://github.com/samwelmunga/JengaAgent --skill btw-samwelmunga
This Skill solves the problem of ad-hoc, unorganized development by providing a structured protocol to capture new features or changes and integrate them into the project's existing Epic and Story hierarchy.
Use the btw skill to capture a new mission for adding a dark mode toggle to the settings page.
High-intent search queries and answers about installing and using this skill.
To capture new project requests, the skill categorizes incoming tasks into an existing Epic and Story hierarchy by determining if they belong to current stories or require new Epics. It then updates board files and summaries to maintain a consistent audit trail.
Tracking ad-hoc feature requests during an agile sprint involves categorizing the stakeholder request within the project hierarchy and updating the project board. This structured approach helps teams decide whether to implement the request immediately or defer it.
Documentation sync updates project board and summary files automatically when new missions are classified. This ensures the audit trail remains consistent and task tracking is accurate across multi-agent development sessions.
Yes, structured project management is facilitated across multi-agent development sessions by capturing user-defined goals and classifying them into the Epic hierarchy. It ensures consistent audit trails and continuous task tracking throughout the workflow.
You need to update project summaries with a new mission classification whenever a stakeholder requests a new feature or change. This ensures the project board reflects the latest goals and maintains an accurate audit trail.
The skill updates existing board files and project summaries to integrate new stories within an Epic. It uses a structured protocol to classify new features and ensures the documentation syncs with the current project hierarchy.
ioniksTurn local Markdown files into a live Kanban board.
orbanReview pending MISTAKE-*.md and SKELETON-*.md reports with Accept, Reject, Discard, Enrich, or Skip options.
script-repoAutomate GitHub issue triage, board synchronization, and sprint planning via AI swarm coordination.
andersnygaardExecute backlog tasks through a .task-board workflow with subagents and Playwright verification.
