Feature-marker
From intent to an executable plan.
Skill-first: PRD, Tech Spec and Tasks artifacts with an installer for agent runtimes.
Problem
Feature requests need clear artifacts before implementation.
My contribution
Development and maintenance of this personal project.
THE PIPELINE / SYSTEM MAP
Feature-marker
The package installs assets; the agent drives work and leaves artifacts in the repository.
Step 1 / 6
Installer & templates
Copy the skill and templates for Claude, Codex or Gemini; the CLI does not execute the workflow.
Step 2 / 6
Agent request
Invoke the skill in a Git project and work on a feature branch.
Step 3 / 6
PRD → Spec → Tasks
Produce readable Markdown files in tasks/{slug}, preserving intent and plan.
Step 4 / 6
Implementation grill
Challenge scope, tests and handoff before implementation; resolve gaps in the artifacts.
Step 5 / 6
Implement & verify
Run tasks and verification inside the agent runtime, preserving unrelated work.
Step 6 / 6
Local commit & handoff
Deliver a branch and push/PR commands. The workflow does not publish or open PRs automatically.
Skill distribution and feature execution have separate responsibilities.
Connections and conditions
- Installer & templates → Agent requestMakes the skill available
- Agent request → PRD → Spec → TasksMakes intent explicit
- PRD → Spec → Tasks → Implementation grillReviews the plan
- Implementation grill → Implement & verifyResolves gaps
- Implement & verify → Local commit & handoffDelivers evidence
Illustrative walkthrough of documented components; it does not run the projects. Sources reviewed on 2026-10-28.
Explore components or play the walkthrough.
Engineering decision
The installer distributes assets; the feature workflow runs inside the agent.
Trade-off
Execution depends on the runtime, while artifacts must remain readable outside it.
Evidence
The package installs the skill and templates; the workflow produces PRD, Tech Spec and Tasks in the repository and ends with a local commit and branch handoff.
Project documentation ↗