Feature roadmap
Publish feature status and timelines with clear expectations.
Customize the recipe
0/1500 characters
Prompt preview
# Feature roadmap Publish feature status and timelines with clear expectations. ## Deliverable A roadmap with documented statuses, sample features and individual feature links. ## Stack and visual direction - Recommended starting stack: Next.js and TypeScript with scoped server-side data access. Start with an explicit persistence and permissions model. - Minimalism: Use deliberate spacing, a compact palette and a clear typographic hierarchy. Retain the labels, feedback and affordances people need to act. Apply this direction to the interface while keeping data and controls easy to read. - Inspect the workspace first. Adapt to its stack when it contains a project, or use the recommended starting stack in a new workspace. ## Tools and setup · Universal Use the receiving agent’s documented skill and tool mechanisms. Match setup to the agent and workspace you actually have. Check available tools first. Propose documented project-level setup only when it materially helps and follow the host's permission prompts. If a tool or integration is unavailable, continue with the workflow below using existing tools, local fixtures or a manual check. Keep secrets in the intended configuration environment. - [Frontend Design](https://github.com/anthropics/skills/tree/main/skills/frontend-design) (Skill) — Plan distinct typography, composition and interaction details before building UI. Fallback: Write a short plan for hierarchy, palette, spacing and interaction states, then review the actual screens against it. - [Next.js](https://github.com/vercel/next.js) (Repository) — Use App Router conventions, server rendering, metadata and accessible route structure. [Official setup](https://nextjs.org/docs/app/getting-started/installation). - [shadcn/ui](https://github.com/shadcn-ui/ui) (Repository) — Use and adapt relevant component source with established keyboard behavior. ## Workflow 1. Model feature cards with status, audience and date confidence. Make items filterable and deep-linkable, and provide a draft review process for updates. 2. Use the simplest implementation that delivers the stated outcome. Follow the user's project constraints and treat the starting stack as a default. Reuse existing work and ask for essential input only when it would change the result. Use realistic labeled sample data when real inputs are unavailable. 3. Run the applicable checks and report what actually passed along with any checks you could not run. ## Acceptance checks - [ ] Filtering by status produces an accurate results set and empty state. - [ ] Unpublished items do not appear in the public catalog or direct route. - [ ] Walk the primary journey with keyboard only. Check visible focus, logical order, accessible names, readable contrast, zoom and reduced motion. Use axe where available and manually check behavior that automation cannot assess. - [ ] Verify real actions and persisted data where required. Exercise relevant loading, empty, invalid, pending, failure and success states. Provide a clear recovery path. - [ ] Use fixtures to verify core flows, including a narrow-screen layout and any applicable permission boundaries.
Recipe resources
Source, setup, and compatibility details.
Frontend Design
Plan distinct typography, composition and interaction details before building UI.
Upstream documents Claude Code.
License · See upstream skill license
Next.js
Use App Router conventions, server rendering, metadata and accessible route structure.
License · MIT
Setup guide for Next.jsshadcn/ui
Use and adapt relevant component source with established keyboard behavior.
License · MIT
Playwright CLI
Walk real browser interactions and collect screenshots or evidence for regressions.
Node.js and supported browser binaries. Use a local build or authorized test environment.
License · Apache-2.0
Setup guide for Playwright CLI