fullstack-implementation

name	fullstack-implementation
description	Implement planned product or code changes phase by phase using repo patterns and verification. Use when the user asks to build, modify, or finish implementation work.

Fullstack Implementation

Use this skill when the task is to implement code, not just plan or advise.

Workflow

1. Identify the active plan from the user request, current context, or plan/*/plan.md; if several candidates exist, inspect their README.md or phase status before choosing.
2. Review the matching research/ notes and current phase file.
3. Follow existing repository patterns before introducing new structure.
4. If unfamiliar APIs, tricky behavior, or implementation trade-offs require external context and the user enabled a relevant MCP, load the matching mcp-* skill first. If crucial context is unavailable, state the assumption or ask a focused question.
5. Implement one phase or one tight slice at a time.
6. Run the narrowest relevant verification first, then broader checks. If verification fails, fix in-scope issues while the evidence points to the current change; record unrelated or environment-caused failures as blockers.
7. Update plan artifacts so another assistant can resume work later.

Required Plan-Aware Behavior

• Treat plan/<topic>-<timestamp>/plan.md as the execution source of truth when a plan exists. If no plan exists and the task is small, proceed with local context; if the task is multi-step or risky, create or request planning artifacts first.
• Update phase checklists or status markers when work completes.
• Record blockers and deviations in the active phase file. Record long-term follow-up work in the active plan README.md or docs when it affects future work.
• If implementation reveals missing context, add it to research/ instead of keeping it only in chat.

Relevant MCP Skills

• mcp-context7 for official framework or library docs
• mcp-github for PR, issue, workflow, or release context
• mcp-figma for design-driven implementation details
• mcp-playwright for browser verification and UI flows
• mcp-sentry for production issue context tied to the change
• mcp-open-bridge for implementation-option comparison, blocker analysis, and focused diff review

Output

Report with:

• Active plan path
• Phase completed or updated
• Files changed
• Verification run
• Blockers or follow-ups