mirror of
https://github.com/magnus919/agent-skills.git
synced 2026-09-11 19:47:12 +03:00
Magnus HedemarkandGitHub
e10508b034
* feat(bmad): add BMad control-plane protocol skill New standalone methodology skill that lets any agent run the BMad method (Breakthrough Method of Agile AI-Driven Development) as a harness-agnostic control-plane protocol: five-field intent contracts, direct/bounded/initiative classification, review-as-triage, failure routing by layer, and autonomy gating with machine-readable spec status. - SKILL.md protocol core with progressive disclosure + When not to use - README.md human-facing install guide - 9 references: protocol, classification, spec, lifecycle, project-context, review-and-failure-routing, autonomy, party-mode, adoption - 4 templates: SPEC, INTENT, STORY, REVIEW - scripts/check-spec.py + 16 tests (stdlib, deterministic spec validation) - evals/evals.json: 9 output-quality cases - Routing seams from bmad to adjacent skills and back from spec-driven-development, product-shaping, implementation-planning, neckbeard - Catalog updates: root README, skill-triggers, marketplace/plugin/llms.txt Closes #399 * fix(bmad): address droid-review findings - check-spec.py: skip headings inside fenced/indented code blocks so a spec cannot PASS on section text that only appears in a code sample - check-spec.py: catch UnicodeDecodeError on non-UTF-8 files and report FAIL instead of crashing - STORY.md template: add created key for resumability/traceability parity - SPEC.md template: split in-progress and in-review status bullets - add 2 regression tests (heading-in-fence, non-UTF-8) * fix(bmad): address droid-review round 2 - check-spec.py: read specs with utf-8-sig so a UTF-8 BOM cannot silently disable the frontmatter status check - check-spec.py: handle standard YAML inline comments after status values (status: draft # pending review) without a false FAIL - references/protocol.md: make lifecycle phrasing consistent with lifecycle.md — four phases plus a learning closeout - add 2 regression tests (BOM, inline comment) * fix(bmad): tolerate trailing whitespace on frontmatter delimiters A spec whose --- delimiter lines carry trailing spaces or tabs would silently disable the status check and let an invalid status PASS. Relax the delimiter pattern and add a regression test. * fix(bmad): ignore inline comments in quoted status values * fix(bmad): tolerate leading blank lines before frontmatter * fix(bmad): fail closed on unparseable frontmatter, matching fence markers Address droid-review round 5 and 6 findings as a single closed class: - Fail closed when a file opens with a --- delimiter that cannot be parsed, so no whitespace/frontmatter permutation can silently disable the status check (previously: unparseable frontmatter was treated as 'no status' warning, letting an invalid status PASS). - Track fence opener markers in collect_headings so a mismatched fence no longer closes a code block early (false-PASS on missing sections) and an unclosed fence no longer swallows real headings. - Accept empty well-formed frontmatter (---\n---) and closing delimiters without a trailing newline. - STORY.md template: parent-spec points at the sibling SPEC.md. - README: status vocabulary is not a strict linear chain; blocked is a resumable routing signal. Whitespace/frontmatter mutation sweep: 9 formatting variants x valid/invalid status all verdict correctly; malformed delimiters fail closed. 29 tests.
178 lines
4.3 KiB
JSON
178 lines
4.3 KiB
JSON
{
|
|
"name": "magnus919",
|
|
"version": "1.0.0",
|
|
"description": "AI agent skills — reusable workflows, protocols, and knowledge packs for agentic systems.",
|
|
"author": {
|
|
"name": "Magnus Hedemark",
|
|
"url": "https://github.com/magnus919"
|
|
},
|
|
"homepage": "https://github.com/magnus919/agent-skills",
|
|
"repository": "https://github.com/magnus919/agent-skills",
|
|
"license": "MIT",
|
|
"keywords": [
|
|
"agent-skills",
|
|
"engineering",
|
|
"product",
|
|
"research",
|
|
"infrastructure",
|
|
"methodology"
|
|
],
|
|
"skills": [
|
|
"./actuarial-risk-modeling",
|
|
"./adr-authoring",
|
|
"./aeo",
|
|
"./agent-council",
|
|
"./agent-evals-and-observability",
|
|
"./agent-production-operations",
|
|
"./agent-skills",
|
|
"./ai-governance",
|
|
"./ai-operating-economics",
|
|
"./anydoc",
|
|
"./api-design-and-evolution",
|
|
"./artifact-pyramids",
|
|
"./ascii-city-engine",
|
|
"./autogen",
|
|
"./backend-engineering",
|
|
"./binary-analysis",
|
|
"./bmad",
|
|
"./brand-designer",
|
|
"./c4-diagramming",
|
|
"./capacity-and-cost-engineering",
|
|
"./chief-of-staff-methodology",
|
|
"./cli-builder",
|
|
"./cncf-landscape",
|
|
"./color-management",
|
|
"./conditional-customer-success",
|
|
"./confluence-cli",
|
|
"./crewai",
|
|
"./crm",
|
|
"./crowdsec",
|
|
"./cyberpunk",
|
|
"./daily-life-discovery",
|
|
"./data-architect",
|
|
"./data-cleaning",
|
|
"./data-engineering",
|
|
"./data-scientist",
|
|
"./de-spin",
|
|
"./digital-twin",
|
|
"./docker-compose",
|
|
"./documents",
|
|
"./dsm5",
|
|
"./dspy",
|
|
"./email",
|
|
"./enterprise-architecture",
|
|
"./epub",
|
|
"./esp32-development",
|
|
"./financial-modeling",
|
|
"./fireflies",
|
|
"./flaresolverr",
|
|
"./flaresolverr-cli",
|
|
"./forgejo-cli",
|
|
"./forward-deployed-engineering",
|
|
"./frontend-engineering",
|
|
"./genius-life",
|
|
"./ghost-cli",
|
|
"./github-runner",
|
|
"./go-to-market",
|
|
"./grafana",
|
|
"./gutenberg",
|
|
"./haystack",
|
|
"./hugo-theme",
|
|
"./implementation-planning",
|
|
"./incident-learning",
|
|
"./jellyfin-cli",
|
|
"./jira-cli",
|
|
"./jira-jql",
|
|
"./kanban-guru",
|
|
"./kubernetes",
|
|
"./langchain",
|
|
"./langgraph",
|
|
"./lastfm",
|
|
"./legal-strategy",
|
|
"./life-coach",
|
|
"./linear",
|
|
"./litellm",
|
|
"./llama-cpp",
|
|
"./llamaindex",
|
|
"./mermaid-diagrams",
|
|
"./meshcore-packet-capture",
|
|
"./migration-engineering",
|
|
"./ml-engineering",
|
|
"./mobile-development",
|
|
"./multi-tenant-saas-architecture",
|
|
"./neckbeard",
|
|
"./notion",
|
|
"./nous-branding",
|
|
"./open-knowledge-format",
|
|
"./openlibrary-cli",
|
|
"./opensource-contributions",
|
|
"./operational-design",
|
|
"./org-design",
|
|
"./pace-plan",
|
|
"./peertube",
|
|
"./platform-engineering",
|
|
"./playwright",
|
|
"./postgres",
|
|
"./privacy-engineering",
|
|
"./product-adoption",
|
|
"./product-analytics-and-measurement",
|
|
"./product-design-and-ux",
|
|
"./product-discovery",
|
|
"./product-experimentation",
|
|
"./product-lifecycle",
|
|
"./product-lifecycle-learning",
|
|
"./product-methodology",
|
|
"./product-operations-and-governance",
|
|
"./product-roadmapping-and-portfolio",
|
|
"./product-shaping",
|
|
"./product-strategy",
|
|
"./production-excellence",
|
|
"./production-readiness",
|
|
"./programming-principles",
|
|
"./promise-theory",
|
|
"./pydanticai",
|
|
"./qa-methodology",
|
|
"./raleigh",
|
|
"./release-engineering",
|
|
"./remote-systems-administration",
|
|
"./research-and-vault",
|
|
"./research-methodology",
|
|
"./resilience-and-recovery",
|
|
"./restic",
|
|
"./secure-software-engineering",
|
|
"./security-audit-methodology",
|
|
"./semantic-spacetime",
|
|
"./seo-audit",
|
|
"./site-reliability-engineering",
|
|
"./slack",
|
|
"./software-architecture",
|
|
"./software-architecture-analysis",
|
|
"./spec-driven-development",
|
|
"./strategy-frameworks",
|
|
"./stripe",
|
|
"./supabase",
|
|
"./systematic-debugging",
|
|
"./tailscale",
|
|
"./technical-documentation",
|
|
"./technology-radar",
|
|
"./telemetry",
|
|
"./tempest-cli",
|
|
"./terraform",
|
|
"./three",
|
|
"./tmdb-cli",
|
|
"./traefik",
|
|
"./trakt",
|
|
"./transistor",
|
|
"./travel-guide",
|
|
"./vercel-eve",
|
|
"./verification-methodology",
|
|
"./vllm",
|
|
"./web-accessibility",
|
|
"./woodpecker-ci",
|
|
"./workflow-architect",
|
|
"./writers-helper",
|
|
"./yc-default-alive-calculator",
|
|
"./yc-weekly-growth-compass"
|
|
]
|
|
}
|