Execute complete feature implementation workflow
Executes complete feature implementation workflow from Linear issue to merged PR with quality gates.
/plugin marketplace add greyhaven-ai/claude-code-config/plugin install linear@grey-haven-pluginsfeature description or Linear issue IDExecute complete feature workflow for: $ARGUMENTS
<ultrathink> Step-by-step through entire lifecycle. Meticulous. Thorough. Zero technical debt. </ultrathink> <megaexpertise type="full-stack-developer"> The assistant should use Linear integration for structured development with project-based organization where each issue = one branch/PR, maintaining clean history and production-ready code. </megaexpertise> <context> Implementing feature: $ARGUMENTS Need complete workflow from Linear issue to merged PR </context> <requirements> - Linear project for feature organization - Separate issues for each major component - One branch/PR per issue - Full error handling and tests - Quality checks at each step - Comprehensive PRs with Linear links </requirements> <actions> 1. Check/Create Linear project: - Check existing: mcp_linear.list_projects(teamId, includeArchived=false) - Find or create: project = mcp_linear.create_project(name="[Feature] $ARGUMENTS", teamId) 2. Create focused issues within project: - Design Issue: Architecture and data models - Implementation Issue: Core business logic - API Issue: Endpoints and contracts - Frontend Issue: UI components (if applicable) - Testing Issue: Test suite implementation - Documentation Issue: User and API docs 3. For each issue: - Get branch: mcp_linear.get_issue_git_branch_name(issueId) - git checkout -b {branch} - Mark "In Progress" in Linear - Implement with full error handling - Write comprehensive tests - Commit with Linear magic words (use actual team ID like ENG, DES, CVIREC, etc.): - Use "Fixes [TEAM]-123" to auto-close issue on merge - Use "Refs [TEAM]-123" to link without closing issue - Other closing words: close, resolve, complete - Non-closing words: ref, references, part of, related to - Push and create PR with magic words in title or description - Branch name should include issue ID for auto-linking (e.g., username/eng-123-description) - Link PR to Linear issue - Update to "Done" when merged (or auto-completed via magic words) 4. Quality gates per PR: tests pass, linting clean, docs updated 5. Track progress via project view in Linear </actions>The assistant should execute workflow completely where each step builds on previous with the goal of production-ready feature with zero technical debt.
Take a deep breath in, count 1... 2... 3... and breathe out. The assistant is now centered and should not hold back but give it their all.