Observed Signal · Jun 15, 2026 · Technical Release · Source: DEV Community · Impact: 2/5 · Sentiment: Neutral
Tool Enforces PRDs/ADRs Upstream in AI Coding
Software engineer João Moura describes upstream, an open tool that enforces creation or linking of PRDs (Product Requirement Documents) and ADRs (Architectural Decision Records) at the moment a developer begins an AI-assisted coding session. upstream integrates with Claude Code via a UserPromptSubmit lifecycle hook that triggers an orchestration skill called upstream-guard. The guard classifies work (feature/bug/etc.), checks for required PRD/ADR content, allows documented bypasses or skipped-justifications, and releases the session to development once documentation requirements are satisfied. The plugin lives in a .claude/ directory and can be initialized with an npm package (upstream-docs); the project is hosted at github.com/joaos-moura/upstream-docs. Moura argues this upstream enforcement reduces post-hoc rationalizations and addresses documentation timing gaps amplified by fast AI coding tools.
A developer tooling release that integrates LLM coding assistants with documentation enforcement; useful for engineering teams but not an industry-shifting announcement for AdTech/MarTech.
Track GitHub Signals & Market Shifts in Real-Time
Polaris7 autonomous intelligence agents track regulatory filings, primary sources, executive changes, and deal flow 24/7. Create your free Explorer workspace to monitor these entities.
Key Takeaways & Evidence Grounding
- João Moura published an article describing upstream, a tool to enforce PRD/ADR creation during AI coding sessions.
- upstream installs a UserPromptSubmit hook into Claude Code that invokes an upstream-guard skill on first prompt submission.
- The upstream-guard classifies work, checks for PRD presence, conditionally checks for ADRs for architecture-impacting features, and releases development once required docs exist.
- The hook fires at most once per session (tracked via a PPID-based cache file in /tmp); bypass branch prefixes (fix/, hotfix/, chore/, docs/) skip the check.
- upstream is available at github.com/joaos-moura/upstream-docs and can be initialized via the npm package upstream-docs (upstream init).
Connected Companies & Entities
2 Entities mappedOntology Mapping & Concepts
Related Market Signals & Shifts
Recent verified developments and strategic activity across this market segment.
Agentic Engineering: PMs Review Artifacts, Not Code
A product manager describes a shift in PM workflows driven by AI coding agents: instead of reading code, PMs should maintain and review the artifact layer (strategy files, agent contracts, CLAUDE.md, tests, evals) that steers agents. The author shipped three projects (PM Brain, Claude Usage for VS Code, Grok Build), ran 800+ tests and LLM-based evals, and published an "AI Shipping Artifact Prompt Pack" (artifact prompts + audit commands). Key practices include a single source-of-truth document for agents, triage rules that combine soft steering with mechanical guardrails, cross-model review to catch blind spots, and converting failures into permanent tests or policies. The piece argues prototypes and agent-driven builds now often precede full alignment, so artifact maintenance and selective human pushback are the primary PM responsibilities when working with agentic systems.
CLAUDE.md Shaped AI-Assisted Development Practices
The author describes how a CLAUDE.md skills file (originally from Andrej Kaparthy) influenced their AI-assisted software development workflow. The file defines four behavioral guidelines — Think Before Coding, Simplicity First, Surgical Changes, and Goal-Driven Execution — intended to reduce common LLM coding mistakes and bias responses toward caution. The article discusses practical implications (e.g., limiting scope, making surgical edits, and defining verifiable success criteria), touches on licensing concerns around AI-generated code (referencing CodeBerg's ban), and notes broader issues such as model provenance, paid access to large models, and preferences for models trained on verified technical sources. The author frames the file as a practical guardrail for collaborating with LLMs rather than replacing engineer judgment.
Open-source Deterministic Tool Catches Rogue AI Coding Agents
A developer published an open-source tool (v1.0) that detects misbehavior from AI coding agents by using deterministic checks instead of LLM-based analysis. The suite runs as a CI gate and inspects diffs, config files and agent transcripts to flag permission escalations, undeclared network calls, contradictory configs and other drift between an agent's stated intentions and shipped changes. The author argues deterministic rules are reproducible, auditable, fast, local and avoid hallucinations, while probabilistic LLM layers should only be advisory. The project contains a core library, five detectors, a live monitor and a meta-reviewer, and includes a demo “rogue” PR that triggers all detectors. Source code, demo and docs are published on GitHub. Publication date: 2026-05-24.
Track Real-Time Market Signals & Shifts
Set up custom watchlists to receive automated, evidence-grounded executive digests whenever material signals or shifts occur across your tracked landscape.