🤖 Generated by the Daily AI Engineer
Part of #49 (child 1 — design-first, per the ADR-0001/#43 and ADR-0002/#54 precedent).
Problem: #49 is epic-shaped: it wants a plugin that lets a non-technical vibe coder build apps on the devantler-tech stack from plain conversation. Before any bundling work, the load-bearing design decisions need settling — otherwise the plugin blurs into the existing agentic-engineering / engineering-practices / automated-ai-engineer audiences (the maintainer's steer on #49 makes the vibe-coding vs agentic-engineering distinction load-bearing), and the stack-boundary guardrail (#49 AC5) risks being hard-coded where it should be configuration.
Proposed direction: one documentation-only ADR (docs/adr/0003-…) settling: (1) plugin shape — a new plugins/vibe-coding agents+skills bundle, distinct from the three existing engineering-facing audiences; (2) the needs→stack mapping skill family and its canonical home in agent-skills (the agent-skills#56 twin), bundled never hand-copied; (3) the allowed-stack guardrail as a consumer-supplied contract section (ADR-0002's role-vs-configuration volatility split), failing closed with a friendly decline + suggested issue; (4) the jargon-free voice/persona conventions with glossary indirection. Follow-up children (skills extraction, plugin assembly, consumption/E2E) are filed once the ADR is accepted.
Rough size: S (one ADR document; no manifest or CI change).
Part of #49 (child 1 — design-first, per the ADR-0001/#43 and ADR-0002/#54 precedent).
Problem: #49 is epic-shaped: it wants a plugin that lets a non-technical vibe coder build apps on the devantler-tech stack from plain conversation. Before any bundling work, the load-bearing design decisions need settling — otherwise the plugin blurs into the existing
agentic-engineering/engineering-practices/automated-ai-engineeraudiences (the maintainer's steer on #49 makes the vibe-coding vs agentic-engineering distinction load-bearing), and the stack-boundary guardrail (#49 AC5) risks being hard-coded where it should be configuration.Proposed direction: one documentation-only ADR (
docs/adr/0003-…) settling: (1) plugin shape — a newplugins/vibe-codingagents+skills bundle, distinct from the three existing engineering-facing audiences; (2) the needs→stack mapping skill family and its canonical home in agent-skills (the agent-skills#56 twin), bundled never hand-copied; (3) the allowed-stack guardrail as a consumer-supplied contract section (ADR-0002's role-vs-configuration volatility split), failing closed with a friendly decline + suggested issue; (4) the jargon-free voice/persona conventions with glossary indirection. Follow-up children (skills extraction, plugin assembly, consumption/E2E) are filed once the ADR is accepted.Rough size: S (one ADR document; no manifest or CI change).