discovered-work-summary
Skill2 starsChanged 19 days agoApache-2.0View on GitHub
Generate summary of discovered work for daily standups or weekly reports. Groups by type/priority, lists Jira issues created, provides stats and trends. Use when user says "discovered work summary" or as part of standup_summary/weekly_summary.
In this repository124 other files it gives its agents.
- add-projectSkill
- ansible-configure-vmSkill
- api-smoke-testSkill
- appinterface-checkSkill
- attach-session-to-jiraSkill
- aws-rds-debugSkill
- beerSkill
- bootstrap-all-knowledgeSkill
- bootstrap-knowledgeSkill
- build-persona-styleSkill
- cancel-pipelineSkill
- cert-checkSkill
- check-ci-healthSkill
- check-integration-testsSkill
- check-mr-feedbackSkill
- check-my-prsSkill
- check-secretsSkill
- ci-retrySkill
- cleanup-branchesSkill
- cleanup-stale-executionsSkill
- clone-jira-issueSkill
- close-issueSkill
- close-mrSkill
- cloud-inventorySkill
- coffeeSkill
- compare-optionsSkill
- create-jira-issueSkill
- create-mrSkill
- create-slide-deckSkill
- data-migration-verifySkill
- debug-local-dbSkill
- debug-prodSkill
- deploy-to-ephemeralSkill
- dev-workflow-orchestratorSkill
- edit-slide-deckSkill
- email-digestSkill
- environment-overviewSkill
- explain-codeSkill
- export-presentationSkill
- extend-ephemeralSkill
- find-similar-codeSkill
- gather-contextSkill
- gdrive-researchSkill
- gke-cluster-opsSkill
- hello-worldSkill
- hotfixSkill
- inscope-researchSkill
- investigate-alertSkill
- investigate-service-issuesSkill
- investigate-slack-alertSkill
- jira-hygiene-allSkill
- jira-hygieneSkill
- knowledge-refreshSkill
- konflux-statusSkill
- learn-architectureSkill
- learn-patternSkill
- list-presentationsSkill
- local-build-testSkill
- local-dev-environmentSkill
- manage-local-servicesSkill
- The first 60 shown.
The file
Files
Discovered Work Summary
Generates daily/weekly summaries of discovered work items. Run sync_discovered_work first for best results.
Inputs
| Input | Type | Default | Purpose |
period | string | "daily" | "daily" (1 day), "weekly" (7 days), or number of days |
include_pending | bool | true | Include items not yet synced to Jira |
include_synced | bool | true | Include items already synced |
format | string | "markdown" | "markdown", "slack", "brief" |
Workflow
1. Load Data
- Compute period days (daily=1, weekly=7, or parse number)
- Load discovered work from memory:
get_discovered_work_for_period(days),get_discovered_work_summary()(via memory/scripts)
2. Analyze Trends
- Daily average, most common type, busiest day
- Sync rate (synced/total), pending backlog
3. Build Summary
- Markdown/Slack: Header, Quick Stats, Jira Issues Created, By Type, By Day, Pending items, Insights
- Brief: One-line "Discovered: X | Synced: Y | Pending: Z"
4. Log Session
memory_session_log("Generated discovered work summary", "Period: ... Items: ...")
Output
Formatted summary. Stats: discovered, synced, pending_backlog, jira_keys, by_type.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.